Maybe the way that FreeBSD does their source management would be a good approach for ww/xwork/open symphony?
They always have HEAD/CURRENT which is the latest and greatest, they then branch off from there to create the various versions. For example: XWORK 2.0 would be HEAD/CURRENT 1.3 1.2 1.1 If there is any significant change that is necessary from an architectural point of view that would become part of HEAD or CURRENT. If there is a bug that is found in CURRENT or 1.3 the developers would then move the fix (lets say it was a simple varObject = null; fix) to each source tree to that users of the code could maintain their versions. As more and more versions of the code come out (and more stable versions) people will not necessary update their code for a production site. I know that they systems I work with have a very rigorous regression testing process because of the critical nature of the application. Having to move the code to a new version may seem like a small thing, but I would never feel comfortable betting my clients million dollar mission critical applications on it. Justen Stepka ----- Original Message ----- From: "Bill Lynch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 14, 2003 11:43 AM Subject: Re: [OS-webwork] Scope for 1.4 > Kirk, > > > I think new users will tend to download the most stable version of a product > > instead of the latest cutting edge version especially when documentation is > > lacking. > > > > What do you guys think? Is 1.2 a lost cause at this point? Is it better > > to focus on the 1.3 release only? > > I agree completely - I think we should definitely keep up with the 1.x branch in > terms of bugfixes and new releases. I feel that 1.3 should be released when it's > ready to go and then we create a list of items to do for 1.4, 1.5, 1.x. XWork > will be great, but it'd be unfortunate to let development on WW 1.x stagnate. > > Regards, > --Bill > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
