You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by Jeremy Hughes <hu...@apache.org> on 2006/07/10 11:08:42 UTC

when to branch

I think it's interesting that we're starting to do parallel
development in separate branches. I've picked out a few guidelines
from  'Rules for Revolutionaries' [1] on the incubator site. I think
the branches 'WODEN-40' and the one John is going to create are only
mini-revolutions, IMO it's worth following the guidelines though...

1) Any committer has the right to go start a revolution. They can
establish a branch or seperate whiteboard directory in which to go
experiment with new code seperate from the main trunk. The only
responsibility a committer has when they do this is to inform the
developer group what their intent is, to keep the group updated on
their progress, and allowing others who want to help out to do so. The
committer, and the group of people who he/she has a attracted are free
to take any approaches they want to free of interference.

2) When a revolution is ready for prime time, the committer proposes a
merge to the -dev list. At that time, the overall community evaluates
whether or not the code is ready to become part of, or to potentially
replace the, trunk. Suggestions may be made, changes may be required.
Once all issues have been taken care of and the merge is approved, the
new code becomes the trunk.

So when WODEN-40 is ready for merge I'll post to woden-dev for a vote
to merge back into trunk.

Any comments?

[1] http://incubator.apache.org/learn/rules-for-revolutionaries.html

Cheers,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org


Re: when to branch

Posted by John Kaputin <KA...@uk.ibm.com>.
Sounds good to me.

John Kaputin



                                                                           
             "Jeremy Hughes"                                               
             <hughesj@apache.o                                             
             rg>                                                        To 
             Sent by:                  woden-dev@ws.apache.org             
             jpjhughes@gmail.c                                          cc 
             om                                                            
                                                                   Subject 
                                       when to branch                      
             10/07/2006 10:08                                              
                                                                           
                                                                           
             Please respond to                                             
             woden-dev@ws.apac                                             
                  he.org                                                   
                                                                           
                                                                           




I think it's interesting that we're starting to do parallel
development in separate branches. I've picked out a few guidelines
from  'Rules for Revolutionaries' [1] on the incubator site. I think
the branches 'WODEN-40' and the one John is going to create are only
mini-revolutions, IMO it's worth following the guidelines though...

1) Any committer has the right to go start a revolution. They can
establish a branch or seperate whiteboard directory in which to go
experiment with new code seperate from the main trunk. The only
responsibility a committer has when they do this is to inform the
developer group what their intent is, to keep the group updated on
their progress, and allowing others who want to help out to do so. The
committer, and the group of people who he/she has a attracted are free
to take any approaches they want to free of interference.

2) When a revolution is ready for prime time, the committer proposes a
merge to the -dev list. At that time, the overall community evaluates
whether or not the code is ready to become part of, or to potentially
replace the, trunk. Suggestions may be made, changes may be required.
Once all issues have been taken care of and the merge is approved, the
new code becomes the trunk.

So when WODEN-40 is ready for merge I'll post to woden-dev for a vote
to merge back into trunk.

Any comments?

[1] http://incubator.apache.org/learn/rules-for-revolutionaries.html

Cheers,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org