I was just trying to use the best example I could think of. My thinking ran the lines of:
There are people in production using the Si's Financial module in production, and I didn't think it would be possible for these people to update to the latest svn trunk during the development of the accounting module as there would probably be conflicts. If I'm wrong, that's great... but it's likely to cause some real trouble if an update ever caused any mistakes. Finally I think you and I are thinking along the same lines from Jacques original idea. The Apache Lab is really great for collaborative projects that stand apart from the svn source tree, but it's better to bring the developments as close to the svn trunk as possible to ease the source conflicts. On Sat, 2007-01-27 at 20:25 -0700, David E. Jones wrote: > On Jan 27, 2007, at 3:19 PM, Daniel Kunkel wrote: > > > I think you may be on to something great here, however I still > > wonder if > > a branch and merge would work even better. > > > > For the fun of it, I'll take an example David mentioned a while > > back, a > > clean room accounting system. This is a large project that is > > likely to > > take a long time to develop, even in a collaborative environment, and > > will probably require significant testing before being dumped into svn > > trunk. > > > > Because it's likely to take a long time during development, a > > branch and > > merge might make more sense instead of merging and upgrading in the > > way > > Jonathan mentioned, since there are likely to be lots of conflicts > > that > > will need to be resolved over time. > > Why not build that, as with everything else in OFBiz, directly into > the main code base? That's certainly how I would do it... > > The main reason to use a branch is when you need to break existing > functionality and leave it broken for an extended period of time. > When adding new functionality even if it is incomplete it can, and > most definitely should, go right into the trunk as the work is done. > > -David >
