Andrés G. Aragoneses wrote:
> 5) If not, would it be interesting to implement it? (Would the feature
> get committed if contributed?)
I seriously doubt that this feature would be accepted in the core code.
It would implement a workflow that seems ways too narrowly defined for
a general purpose tool like Subversion. I'm also not aware of any
existing tool that does anything like this for Subversion; some of the
distributed version control systems (like git) have some elements of
this workflow (specifically that anyone can commit to "their branch" and
someone else can determine which changes should be merged to the "main
stream").
You could certainly wrap something around Subversion to accomplish this:
imagine a web app that automatically hands out novice commit ID's and
precreates a branch for them and updates the security stanza.
Maintainers would simply be set up to have rights to the main project
and get commit e-mails for anything under their purview...
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-02 20:54:28 CEST