On 4/7/2010 3:47 PM, Greg Troxel wrote:
Christian Boos<[email protected]> writes:
On 3/23/2010 12:43 AM, Greg Troxel wrote:
Speaking as someone using trac seriously, it seems scary to be talking
about a 0.12 release that depends on unreleased versions of other tools.
I understand and share your concerns.
If that's really the case, then I'd say the other tools need to be
encouraged/helped to get to release or forked and released before 0.12
has an rc.
We have considered that. It looks like we're going to have a Babel
0.9.5 really soon (I see the packages on ftp.edgewall.org as I'm
writing this), and perhaps a Genshi 0.6 release at some later point
(keep finger crossed).
The fact remains that those libraries are currently strong
dependencies for Trac (Genshi even more so than Babel), and neither
has currently the level of maintenance we were used to have, every
sign indicates this trend won't change. I've also stopped to hope
there will be any drastic performance improvement, and while there has
been some improvements last year (1), I rather feel that this means
that all that could be realistically done has now been done on this
topic. Of course, theoretically someone could step up anytime and
bring in a radically new idea and dramatically increase performance,
but that's precisely what I've been hoping for since the last 4
years. While there has been such attempts, made by bright minds, none
really succeeded.
Thanks for the detailed explanation. Everything you say sounds quite
reasonable in term of how trac got where it is and the way forward.
But, if Genshi doesn't have a release that can be used (reasonably) with
trac, then it should be a small matter of making a tarball from Genshi's
CM ystems and calling it Genshi-0.5.80 or GenshiTrac-0.5.80 if it's
socially awkward to call it Genshi-0.6. Then packaging systems can
either update their Genshi package or make a GenshiTrac package, and
there's no more packaging issue. (I realize this doesn't address the
lack of maintainer time issue. But if something in svn is good enough
and required, it should be declared a release before 0.12 is in RC.)
That's why we won't after all release a 0.12rc1 directly, in the coming
days, but first make a 0.12beta. I hope it's more acceptable to have a
"beta" version depending on an unreleased package than a RC :-)
We'll then release the 0.12rc1 version after the Genshi 0.6 release.
But if it's still not released in a month or so from now, then we could
indeed integrate the genshi/ files as tracdep/genshi.* and make sure
that the Trac plugins importing the genshi modules will actually find
our tracdep.genshi ones (hopefully a `sys.modules['genshi'] =
tracdep.genshi` will be enough).
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
