Exactly. I fully expect to see additional commits before we release.
They should be primarily bug fixes, but minor updates such as this are
OK too. We just want to avoid any major changes from here on in.
On Nov 17, 2009, at 12:30 PM, Todd Volkert wrote:
Don't worry about it - we're not tagging in the next few days or
anything;
it's more that we should be winding down our new feature commits and
focusing on stability in preparation for our graduation (and the 1.4
release
that will follow thereafter).
-T
On Tue, Nov 17, 2009 at 12:19 PM, Christopher Brind <
[email protected]> wrote:
Damn, I must have checked out the code read only or something as I'm
getting
a forbidden response. Will have to commit it on Thursday now - if
you want
to freeze before then that's OK, I'll work around it.
Cheers,
Chris
2009/11/17 Todd Volkert <[email protected]>
Sounds fine to me
On Tue, Nov 17, 2009 at 11:53 AM, Christopher Brind <
[email protected]> wrote:
Am I OK to commit my changes to the SerializationExcepton and those
other
serializer changes we discussed?
Cheers,
Chris
2009/11/17 Sandro Martini <[email protected]>
Hi Todd,
Sandro, no need to keep a local copy of DigestAuthentication as a
backup
--
the SVN server will keep the historical copy for you.
Ok, but so in the meantime I could proceed with finishing it.
For Greg:
Yes, we want to only include functional and tested code in the
1.4
release.
the code in DigestAuthentication is working (the related unit test
works good with apache 2.2.x), but as you said to me, it hasn't
the
right flow inside. So at this point I don't know if you prefer to
remove it (and its unit test) temporary (in any case) or to keep
and
mark as experimental, but no problem whatever you choose.
In you give me some days (until mid on next week, or it is too
later
?) I can finish it, so if you can wait to remove it it will be
simpler
also for me to do tests, otherwise anytime I synchronize from the
trunk (using the replace all for security) i miss my local files
inside the project.
Byeeee
