Remy Maucherat wrote: > I consider 4.1.x can recieve bug fixes and minor feature additions > (example: the JNDI realm new feature which just got added, > optimisations, etc ...), similar to HTTPd 2.0. This is consistent with > the patches I and others have been applying, the release process we've > been following, and so on.
+1 If there is enough interest and committers that need that feature - I see no problem with that. As procedure, I think it would be nice to announce the new features before commiting them. IMO the best way to improve this in future is to separate the 'core' and modules, or at least have a separate directory for add-on features and modules. This way the 'core' release can be frozen, but new features can be easily added. Given the backward compatibility it is even possible to even share the modules for multiple tomcat versions ( probably some doc should mention if it was tested with 4.0, 4.1 or 5.0 ). This may also increase the release cycle and reduce the load for the RM ( or at least allow the load to be spread - since modules could be released separately ). Costin -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
