Subject: Re: [boost] Respecting a projects toolchain decisions
From: Klaim (mjklaim_at_[hidden])
Date: 2010-12-29 06:49:08
I know about the 7 years existence of the ticket, but if you follow closely
the (very) recent evolution of TRAC, or simply look at the features of the
(late) coming version :
about how it will be achieved is there :
The related tasks planned are there :
You see that it's planned (at least). It was not planned before as you
pointed it correctly.
<http://trac.edgewall.org/wiki/MultipleProjectSupport>However, I agree that
you can't count on it at the moment neither in near future, so if
multi-projects management becomes a requirement, TRAC can't be kept and
Redmine and Jira becomes the only good alternatives. I personally prefer
Redmine but would still like it to be more mature in some aspects.
On Wed, Dec 29, 2010 at 03:15, Dave Abrahams <dave_at_[hidden]> wrote:
> At Tue, 28 Dec 2010 15:02:07 +0100,
> Klaim wrote:
> > >No, I mean that I'll be opposed to visiting 4 different issue trackers
> > for 4 different components I maintain. I want to see a single list of
> > issues on my plate, so that I can prioritise them together.
> > Isn't it more a issue tracking problem? TRAC is well known to be able to
> > manage only 1 project (that will change with coming versions)
> No, it won't. Do you know how old that feature request is? 7 years
> (http://trac.edgewall.org/ticket/130)! A few years ago I gave up
> waiting for the Trac people to handle it and authored an extension to
> do that:
> and couldn't maintain it. Very happily using Redmine now.
> Dave Abrahams
> BoostPro Computing
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk