I guess a manual process will still be needed in order to turn any kind of
automated build into an official stable version, unless automated test are
covering 100% of potential regressions (wild dream, I guess:) ).
My question about TomEE / TomEE+ upgrade process is meant to (when it'll be
solved)
First, love the name :)
On Jul 16, 2012, at 12:31 PM, Alex The Rocker wrote:
> We are considering Apache TomEE+, but we are concerned by the lack of clear
> update policy of Tomcat version in TomEE & TomEE+.
[..]
> it
> would be nice to have a clear statement on Apache TomEE/TomEE+ update
> polic
i spoke about the snapshot which uses t7.0.29
- Romain
2012/7/16 Alex The Rocker
> Well, the "Download" tab (http://openejb.apache.org/downloads.html) show a
> list of fixes for TomEE / TomEE+ 1.0 which show that Tomcat version is
> 2.0.27 (we understand that were was a typo and 7.0.27).
> Whe
Well, the "Download" tab (http://openejb.apache.org/downloads.html) show a
list of fixes for TomEE / TomEE+ 1.0 which show that Tomcat version is
2.0.27 (we understand that were was a typo and 7.0.27).
Where is it mentionned that Tomcat 7.0.29 is part of 1.0, if it is ?
Alex
On Mon, Jul 16, 2012
Hi,
we have no official position regarding it from what i know but here two
points:
1) if you look last update of tomcat or security update (i think of cxf) it
took < 2 days for the snapshot (we are already on tomcat 7.0.29)
2) regarding releases we are working on the 1.1.0 and then we'll refactor
Hello,
We are considering Apache TomEE+, but we are concerned by the lack of clear
update policy of Tomcat version in TomEE & TomEE+.
Today (16th of July 2012):
- Apache TomEE(+) 1.0 is available with embedded Apache Tomcat 7.0.27
- Apache Tomcat 7.0.29 is available since 8th of July.
Although