tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rémy Maucherat <r...@apache.org>
Subject Re: Tomcat 8.next
Date Thu, 03 Mar 2016 15:59:17 GMT
2016-03-03 16:41 GMT+01:00 Christopher Schultz <chris@christopherschultz.net
>:

> Mark,
>
> On 3/1/16 5:12 PM, Mark Thomas wrote:
> > To summarise where I think this discussion is going:
> >
> > - Create 8.5.x from 9.0.x with the following changes
> >   - revert all changes to spec APIs
>
> I would argue that anything that has been added (in TC9) can stay; only
> revert the removals and possibly any deprecations.
>

The plan is not to proactively revert all removals of items deprecated in
TC 8.0.x, only those people will actually complain about.

>
> >   - make any necessary changes to work with Java 7
> >
> > - Release 8.0.x and 8.5.x in parallel for ~6 months then stop 8.0.x
> >   releases
>
> Does this have implications for whether or not we can claim
> spec-compatibility? Tomcat 8.5 would be
> servlet-3.1-except-for-that-Java-7-support-thing... so can we claim that
> Tomcat 8.5 officially supports the servlet 3.1 specification? Do we even
> care?
>

Yes, the Servlet 4 API will likely change and this would mean we'd have to
beak things. It the Servlet 4 API items are removed, then people can use
the equivalent proprietary Catalina classes that can stay unchanged in
Tomcat 8.5. This is not related to the TCK because the ASF has no access to
it.

>
> > - If users report problems caused by removal of a deprecated API in
> >   8.5.x, restore it.
> >
> > Did I miss anything? Any additional concerns to address?
>
> Rémy

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message