13 Nov
2018
13 Nov
'18
11:25 a.m.
So I’m proposing:
* Tomcat: latest of debian oldstable/stable/unstable for tomcat 8.x, see
https://packages.debian.org/search?suite=default§ion=all&arch=a…
(in practice that’s 8.0.x and 8.5.x).
@Thomas: I see that we provide a tomcat7 and tomcat8 packaging for debian. Should we drop
the tomcat7 one? I don’t think we should support it.
* Jetty: latest of debian oldstable/stable/unstable for jetty 9.x, see
https://packages.debian.org/search?suite=default§ion=all&arch=a…
(in practice that’s 9.2.x). NOTE: Strange that “unstable” is lagging behind so much and
that Jetty 9.4.x is not being tested. Anyway it’s easier to follow the debian repos.
* Jetty Standaline: latest of Jetty 9.x, (i.e. 9.4.x FROM)
I’m updating
https://dev.xwiki.org/xwiki/bin/view/Community/ServletContainerSupportStrat… , let me
know if you disagree.
Thanks
-Vincent
On 31 Oct 2018, at 10:04, Vincent Massol
<vincent(a)massol.net> wrote:
Hi devs,
We now have
https://dev.xwiki.org/xwiki/bin/view/Community/ServletContainerSupportStrat… but it’s
not precise enough.
I’m proposing the following:
* Mention the supported version cycle and mention that we support the latest version of
the cycle.
* For Tomcat, I propose to say we support Tomcat 8.x (which means Tomcat 8.5.34 as of
today, see “latest” tag on https://hub.docker.com/_/tomcat/)
* For Jetty (standalone packaging or standard), I propose to say we support Jetty 9.x
(which means Jetty 9.4.12 as of today, see “latest” tag on
https://hub.docker.com/_/jetty/)
WDYT?
Thanks
-Vincent