Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
On Fri, 6 Apr 2007 14:15:31 -0300, Gerhard Fiedler wrote: > Rick Martin wrote: > >> Don't want to steal the OP thread, but what would you consider to be a LOT >> fo branches? >> I work for a manufactoring company and due to the software design we do an >> official release every two weeks to the factory floor. I'm creating a >> branch for each of these and then creating a tag if we need to release a >> bug fix on the build branch. This creates a fair number of branches and >> tags. Too many? > > I'm not sure I understand your procedure correctly, but couldn't you tag > these official releases, and only branch this tag later if you actually > need to do some bug fixing? Assuming that fixing bugs in an official > release is the exception rather than the rule, this would cut down quite a > bit on the number of branches. > > Gerhard Hi Gerhard, Yes, we can set a tag. In fact I do so we can see the starting point of the branch easily. However, it's not just bug fixes. The design of the software requires coding changes for things that really shouldn't be in code (don't even get me started on that topic). So most releases have partial updates before the next release. Hopefully, some redesign work will get done and we can reduce the partial releases. Thanks, Rick