lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: tomcat6 (Ubuntu Lucid)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: tomcat6 (Ubuntu Lucid)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Why should the LTS follow with non-latest stable tomcat? With the
release of ga tomcat 7 it's safe to assume that tomcat6 has reached
maintenance-only mode.
The changelog from 6.0.28 to 6.0.32 is big, but changes are not
breaking; some more enableable features, mostly conformance fixes or
Ubuntu's policy for Stable Release Updates is about fixing specific
major issues or security vulnerabilities with a minimal patch to reduce
the risk of regression on running machines, and QA the minimal change
extensively. A known issue is better than an unknown regression :
A known issue is better than an unknown regression
Hmm ok; understood and agreed; so a bug like this should be filed for
any known issues in the future and a backport request for others.
My point came from the fact that tomcat6 is widely used as is and
embedded in commericial products as well,
Why should the LTS follow with non-latest stable tomcat? With the
release of ga tomcat 7 it's safe to assume that tomcat6 has reached
maintenance-only mode.
The changelog from 6.0.28 to 6.0.32 is big, but changes are not
breaking; some more enableable features, mostly conformance fixes or
Ubuntu's policy for Stable Release Updates is about fixing specific
major issues or security vulnerabilities with a minimal patch to reduce
the risk of regression on running machines, and QA the minimal change
extensively. A known issue is better than an unknown regression :
A known issue is better than an unknown regression
Hmm ok; understood and agreed; so a bug like this should be filed for
any known issues in the future and a backport request for others.
My point came from the fact that tomcat6 is widely used as is and
embedded in commericial products as well,
** Attachment added: jstack for deadlock
https://bugs.launchpad.net/bugs/787496/+attachment/2140752/+files/jstack.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in Ubuntu.
https://bugs.launchpad.net/bugs/787496
Title:
Fixed in 6.0.27 with
http://svn.apache.org/viewvc?view=revisionrevision=941868 - not exactly
sure it can be directly backported to 6.0.24.
** Bug watch added: Apache Software Foundation Bugzilla #48903
http://issues.apache.org/bugzilla/show_bug.cgi?id=48903
** Also affects: tomcat6 via
Maverick+ ship with 6.0.28+, so this is fixed there. Nominating for
Lucid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in Ubuntu.
https://bugs.launchpad.net/bugs/787496
Title:
tomcat6-user 6.0.24 with confluence
** Attachment added: jstack for deadlock
https://bugs.launchpad.net/bugs/787496/+attachment/2140752/+files/jstack.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787496
Title:
tomcat6-user
Fixed in 6.0.27 with
http://svn.apache.org/viewvc?view=revisionrevision=941868 - not exactly
sure it can be directly backported to 6.0.24.
** Bug watch added: Apache Software Foundation Bugzilla #48903
http://issues.apache.org/bugzilla/show_bug.cgi?id=48903
** Also affects: tomcat6 via
Maverick+ ship with 6.0.28+, so this is fixed there. Nominating for
Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787496
Title:
tomcat6-user 6.0.24 with confluence deadlocks
--
ubuntu-bugs
14 matches
Mail list logo
