On 14/04/2010 12:02, sebb wrote: > On 14/04/2010, Mark Thomas <ma...@apache.org> wrote: >> Please test this release candidate and provide feedback. > > Some bugs reported against Tomcat 7 may require API changes to fix. > Are API changes going to be possible once the RC has been released?
Yes. I still have some Lifecycle changes that will require API changes as may the JMX GSOC project if that gets accepted. One of the things I intend to add to the release notes is a list of APIs that are considered public and fixed. At the moment that is: javax/**/*.class Anything under apache.org is open to change. Folks can use it, but it might change. It would only be an issue for folks working on custom components. As the release matures, we'll fix more of the API. There will , however, always remain some parts of the API that are viewed as internal and subject to change at any time. The idea is that we document this as we go and end up with a clearer definition. > If not, please consider at least reviewing the bugs before committing > to the API. I think it is fair to say that the API is fixed to the extent that we don't want to change it unless we have to. No point breaking backwards compatibility for no good reason. Historically, 'good reason' has equated to 'bug causing pain for user' and similar. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
