I think the concept of focusing on one major feature that defines the
release and having a relatively short release cycle is a good one. I think
if you were to publish these plans, it might be a good idea to specify that
just because release 1.3 will be focused on say "server-client
configuration" that it does not preclude someone from stepping up and
tackling another major feature like atomic renames. It is simply that the
1.3 release timeframe will be determined by the major feature scheduled for
that release. That might help temper any arguments over the schedule.
I think the three features you proposed sound about right. The one I will
toss into the ring is some kind of authz system that works across all of
the RA-methods. Assuming it is somewhat based on mod_svn_authz, I would
like to propose that said system ought to introduce at least one more layer
of authority to be able to specify that someone can only add to a path, as
opposed to add and update. This would help with the tag issue that so many
people seem to object to. You could define authorities on a "tags" folder
such that it would allow tags to be created but not modified. Yes, I am
aware there is a sample hook for this.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 23 03:38:05 2005