[SciPy-Dev] Trac performance?
Charles R Harris
Mon Feb 6 18:39:01 CST 2012
On Mon, Feb 6, 2012 at 3:09 PM, David Cournapeau <firstname.lastname@example.org> wrote:
> On Sun, Feb 5, 2012 at 1:02 PM, Pauli Virtanen <email@example.com> wrote:
> > Hi,
> > 05.02.2012 12:59, Ralf Gommers kirjoitti:
> >> Is there an end in sight for the troubles with Trac? It's driving me
> >> completely crazy. So if not, I'm willing to invest some time in moving
> >> all the relevant content on the Trac wikis somewhere else (suggestions
> >> welcome). I'm thinking about things like development plans, GSOC info,
> >> list of maintainers per module, etc.
> > Newer versions of Trac are supposed to alleviate the "database is
> > locked" error, which is a PITA. So upgrading the software could help.
> > I think moving stuff out from the Trac could be useful in any case, as
> > its account management is not so transparent. As for the developer wiki
> > info --- how about turning on wikis on Github and using them? Does
> > someone have experience on how usable they actually are?
> > As for dropping Trac completely -- last time around, I think the Github
> > issues system lacked features. I think they've added some stuff since
> > then, though.
> They have added milestone, which is something that is a must for
> release management IMO. Otherwise, it is quite limited, but OTOH,
> that's one less thing to worry about, and it is not like trac is a
> great issue tracker either. github actually has a few features that
> are sorely lacking in our current trac, like a decent REST API and
> mass-editing of existing issues.
And github will probably continue to improve issue tracking in the future
at a decent rate. It might make sense to get on that train now instead of
running after the caboose later on.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev