I come from a time when everything was modularize similar to ofbiz. I go by the principle that if one line of code is changed the whole program is suspect for errors. each modules was determined to have it own life cycle. Therefore if only one module is changed it is the only one suspect for errors.
each module was define as a black box with input and outputs. to which other modules would interface. so each module had its own workspace. the team working on a module would notify the other teams when their interface would change effecting the other modules. This would allow each module to be updated with out changing the complete program. so the versioning was at module level and the program version was modified based on the modules versions. so trunk would stay stable each module would have it own branch. someone could move a module into their local version of the trunk to test. but the basic test of the module while in their branch would be against established black box input and output. the would allow a module to advance but not actually effect the trunk till the merge. and as long as the test passed there should not be any merge issues. so each folder of the frame work would be a module under the module framework branch. and each application would be a module under applications branch and so forth. ========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Jacopo Cappellato sent the following on 5/4/2010 12:04 AM: > What if we start evaluating a different way we organize our svn, daily work > and release strategy? > We may try to move in the direction of having a more stable framework and > more dynamic applications. > > A very simple strategy would be the following one: > > all the changes to the framework (that are not bug fixes) are done in a > separate branch (branches/framework-latest or similar); in this way > trunk/framework will only get bug fixes. > Every 6-12 months (or whenever we want - we can discuss about this) we merge > the branches/framework-latest into trunk/framework and fix the > trunk/applications (of course we could do this in a separate temporary > branch). > > What do you think? > > Jacopo > >
