On Wed, Mar 25, 2009 at 11:17 AM, Rainer Jung <rainer.j...@kippdata.de>wrote:
> On 25.03.2009 18:38, Costin Manolache wrote: > >> This thread was more about where to implement new features - if the goal >> is >> a 'redesign >> from scratch' than maybe sandbox or a branch is a better place, but we >> tried >> that twice >> (jk2 and webapp) and I don't think there are enough people interested in >> such an effort - >> development nor testing. Adding the features to the existing code - with >> the >> extra effort to not break existing functionality - IMO has a better chance >> of success. >> > > Thanks Costin for coming back to this topic. Collecting ideas for major > redesigns could be done, but that was not my intention. I don't see enough > time available for doing the big stuff, but I want to proceed committing > time slices for incremental improvement. So I would like to stabilize 1.2 > now (apart form bug fixes), because I think we are in good shape there now, > and open up another line of development (1.3), where implementing new > small/local features, which always includes the risk of introducing new > bugs, can be done without posing any risk on 1.2. What about - release 1.2.28, create a branch for it, then start adding the features in trunk. After you add few features and are ready for a release - we can decide how to name it (1.2.29 or 1.3.0 ), based on how much and what changed. I would only switch to 1.3.0 name if there are backward-incompatible changes - keep in mind many people will be reticent to switch ( and test ) if they assume 'big changes'. I wish we used Ubuntu-like release names :-) Costin > > This thread is more about whether people are against doing that, and if so, > why. > > Regards, > > Rainer > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
