[Rt-devel] Development roadmap

Kevin Falcone falcone at bestpractical.com
Thu May 5 14:10:45 EDT 2011

On Thu, May 05, 2011 at 06:50:13PM +0100, Dominic Hargreaves wrote:
> On Tue, May 03, 2011 at 10:47:39AM -0400, Kevin Falcone wrote:
> > We'll publish an official policy in the next few weeks, but our plan
> > is to try and keep 4.0 to 'bugfixes' while features go to 4.2 and we
> > aim to release 4.2 in the fall.  At that point, 4.2 becomes bugfixes
> > only and we start working on new features for 4.4.
> Okay. I still need to get clear in my head the relative trade-offs
> between being able to install and maintain multiple versions at once
> vs the simplicity of a single package name. Much of it probably depends
> on the frequency of releases relative to Debian's stable release cycle,
> as well as your expectation for the support of older branches.

I'm not exactly sure when having 3.6 and 3.8 installed in parallel is useful.

> > If you can get a request-tracker4 packages instead of
> > request-tracker40/request-tracker42 it would make us all very happy.
> Could you expand on how that would particularly affect you as
> upstreams?

Because if request-tracker4 gets into a stable release, users would be
able to come up to a more recent release of RT without pulling the
patches from testing/unstable.  We encountered a lot of folks
installing 3.6.7 because it was available in Debian and we'd done a
lot of work on 3.8 that they never saw.

We'd love to start getting large releases of RT out the door more than
once a year.  We're still finalizing scheduling and end-of-life plans

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-devel/attachments/20110505/f0f248b4/attachment.pgp>

More information about the rt-devel mailing list