> -----Original Message----- > From: Stephane Nicoll [mailto:[EMAIL PROTECTED] > Sent: 19 March 2004 11:47 > To: Cactus Users List > Subject: RE: R�f. : Cactus integration test with a production's EAR > > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Friday, March 19, 2004 11:44 AM > To: 'Cactus Users List' > Subject: RE: R�f. : Cactus integration test with a production's EAR > > <OT> > Why don't you build everything from CVS HEAD? That would ensure that > changes > are all compatible at any single point in time. I'm curious to understand > why > you don't want to be doing continuous integration (I've always found it to > be > very useful in my projects). If people are working on fixing bugs of a > previous release, they'll work on a branch. Same if people are working on > experimental features. But the main development for the current release > would > be on HEAD. What's wrong with this? :-) </OT> > > Simply because some modules might have been updated to version 2.0 with > new > functionnalities that won't be included in the next version of the > application. So other modules still relies on 1.4.X for instance. The CVS > head is stable but it might not be the state we want for all modules.
Ah, but then you would have a branch called 1.4 which will contain all code to be delivered to release 1.4. You still don't need to have different versions of each modules. They could all be 1.4, no? Anyway that's a project's decision and doesn't affect your initial question... :-) Let me think about your other email. Thanks -Vincent > > Regards, > > St�phane > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
