[request-tracker-maintainers] request tracker in etch

[Niko Tyni]

On Mon, May 21, 2007 at 06:44:03PM -0600, Cedar Myers wrote:
> I've been using 3.6.1 as packaged in Etch but have seen many
> strangnesses I'll call bugs.  I have to assume that Best Practical has
> found many of these, so I haven't spent time reporting anything.

It's your call of course, but reporting them might help other Etch
users struggling with the same problems.
 
> I'm trying to choose which version to use in a production environment.
> What are the chances that request-tracker will be updated to a new
> upstream version (bug #404913) in the near future?  Would this sort of
> change be allowed in an update to Etch, or would I need to pull from
> testing?  Am I better off just using 3.4?  Or should I use the vendor's
> releases directly?

I'll get 3.6.3 into unstable soon, thanks for the reminder.  Any newer
version will not go into Etch however, that's the point of a stable
release. The only changes accepted are targetted fixes for serious
bugs.

I don't think 3.4 is better in any regard at this point, and we will
most probably have it removed from Debian before the next release.

If you can't live with the bugs in Etch, one more option may be
backports.org, which used to carry newer versions of RT for sarge.
This doesn't help right now, though: the packages there are usually
rebuilds from the unstable ones, so there's no RT package there yet
either. Generally, using backports.org packages instead of mixing testing
and stable has the advantage of not pulling along all the libraries
from testing.

Cheers,
-- 
Niko Tyni   ntyni at iki.fi