I'm sure most everyone has noticed the exponential increase in commit
activity coming from Chicago over the last week or two... so there's
no point in beating around the bush here. We've been pushing very
hard to get locking finished, because (1) it's taken way longer than
we expected (the branch was made on Nov 4th!), (2) Collabnet's
customers are dying for this feature, and (3) if we don't get svn 1.2
stabilized and into its "one month freeze" fairly soon, it won't make
it into the next version of Collabnet's product. :-/
The locking branch is now functionally complete. We're merely waiting
for a few code cleanups, and then we'll merge the branch to trunk --
probably within the next day or two.
At that point, we have two aggressive goals:
1. Get everyone to seriously hammer on the locking feature for a
week or so. We can fix bugs as we go, write more tests, etc.
2. Get /trunk stabilized for a 1.2-release branch and freeze.
(Immediately followed by a 1.2-beta1 tarball, as usual.)
Here are the ways in which people can be most helpful:
* If you want to test the locking stuff, that would be fantastic.
But pretty please: please don't start questioning the how and why
of the feature's design/architecture/UI until you've done some
homework. All of those things were fleshed out over months of
conversation last autumn, available in the dev@ mail archives.
There's also a functional-spec and UI-spec in the notes/locking/
area which should guide your testing. (During our one-month
freeze, I'll be officially documenting the feature in the book.)
* Do whatever you can to get /trunk stable. Apply outstanding
patches, test bugfixes, write more tests, etc.
We released 1.0 in Februay, 1.1 in September, and (hopefully)
1.2 in late April. The time is ripe!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 19 13:57:57 2005