Allen Bierbaum wrote: > On Wed, Mar 4, 2009 at 5:06 AM, Gerrit Voss <[email protected]> wrote: >> Hi, >> >> On Tue, 2009-03-03 at 19:13 -0600, Allen Bierbaum wrote:
[snip] >>> 2) Once known major bugs are fixed, create an RC1 branch for >>> testing. (Mar 13) >> As of now I will be traveling on the 12th so doing the RC1 on the 13th >> might be a little tough. I would prefer to try to finish on the 11th. >> Given that this date is a week away, I'm not really sure if this makes >> sense but we should at least give it a try. I also loose access to most >> of my machines after Friday (due to a spatial shift to Germany) so >> somebody else will have to do the final builds. > > IMHO, we don't need 'builds", but could just have people start using > the branch. I think most of the people that will be testing the code > and fixing bugs will be using the source any way right? Personally, I don't think that there should be a release candidate branch. Did you mean tag? (Yes, I know it's all just convention in Subversion, but the psychology of it is important.) I think that a branch should be created for 2.0 maintenance at some point when it is determined that the code base is stable and nearly ready for release. In other words, choose a time to create the branch when there aren't a whole lot of pending changes to make to the trunk that then have to be merged to the branch. That process can be confusing and error prone, especially when scrambling to get a release done. The other factor to consider is that the creation of the 2.0 maintenance branch shouldn't imply that 2.1 development can get fully under way before the 2.0.0 release happens. If major changes start happening on the trunk before the release, critical bug fixes could be lost in the shuffle. One way to force that is to wait until after the 2.0.0 release to make the branch, but that isn't always practical if important work for the next version needs to get started. -Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ The information transmitted in this communication is intended only for the person or entity to which it is addressed and contains proprietary material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
_______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
