Hi folks, > Sorry for the long delay. Myself and, I think, Andrew have been short > on time.
Yes, my apologies, I've been very busy the last couple of months. > The transition is basically ready to go, but I've been rethinking the > need > to drop request-tracker4, given it will all be quite tight. It turns > out that > request-tracker4 is still supported upstream > (https://bestpractical.com/release-policy) > and there's no specific EoL set. When we first started the plan to > deprecate request-tracker4 in Debian, I think we were assuming > otherwise. > The package is in good shape and I believe otherwise ready to be > released. > > If Andrew is in agreement, I therefore think we should let request- > tracker4 > be released with the next release. We can reconsider whether to drop > it from > the release + 1 at a more leisurely pace. The work we've done to date > will not > be wasted effort. Yes, I'm okay with keeping request-tracker4 in Bookworm, as Dominic says, the package is in good shape. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |
