Preparing for Trac 0.12 - New release / packaging suggestions

11 views
Skip to first unread message

Remy Blank

unread,
Apr 5, 2010, 11:48:20 AM4/5/10
to gen...@googlegroups.com, python...@googlegroups.com
Hello,

We're currently preparing to release Trac 0.12rc1. One significant
hurdle is that Trac now depends on Genshi trunk (>=r1072) due to the
i18n functionality, and Babel 0.9.4 has a bug that prevents correct
Polish translations.

While we could ask our users to install Genshi and Babel from SVN, it
would make the installation process even more difficult. Moreover,
packagers would have to either upgrade their Genshi and Babel packages
to non-released versions, or create two packages for each and allow them
to be installed in parallel. I understand this is non-trivial work.

So this boils down to two questions:

- Can we expect Genshi 0.6 / Babel 0.9.5 releases within a reasonable
timeframe (say, a few weeks)?

- If not, do you have any suggestions how we could package Genshi and
Babel with Trac so that they don't interfere with an "official" install?
We have been thinking about using svn:externals to pull in both Genshi
and Babel, and using some import tricks to hide them in a private namespace.

Thanks for any hints.
-- Remy

signature.asc

Christopher Lenz

unread,
Apr 6, 2010, 9:45:08 AM4/6/10
to gen...@googlegroups.com, python...@googlegroups.com
Hi Remy,

On 05.04.2010, at 17:48, Remy Blank wrote:
> We're currently preparing to release Trac 0.12rc1. One significant
> hurdle is that Trac now depends on Genshi trunk (>=r1072) due to the
> i18n functionality, and Babel 0.9.4 has a bug that prevents correct
> Polish translations.
>
> While we could ask our users to install Genshi and Babel from SVN, it
> would make the installation process even more difficult. Moreover,
> packagers would have to either upgrade their Genshi and Babel packages
> to non-released versions, or create two packages for each and allow them
> to be installed in parallel. I understand this is non-trivial work.
>
> So this boils down to two questions:
>
> - Can we expect Genshi 0.6 / Babel 0.9.5 releases within a reasonable
> timeframe (say, a few weeks)?

Yeah, I really hope so. I'm working with asmodai on a Babel release right now. When that's done I'll looking into getting Genshi 0.6 out of the door, which mainly depends on fixing the match template processing regression reported in #370. Any help with that would of course be much appreciated.

Cheers,
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/


Remy Blank

unread,
Apr 6, 2010, 5:04:38 PM4/6/10
to gen...@googlegroups.com, python...@googlegroups.com

This is good news, thanks. Having official releases is certainly the
simplest option for us. I understand Babel is well on its way (from
rumors on IRC). I know it's always delicate to talk about schedules in
open-source projects, but do you have a ballpark estimate for the 0.6
release timing?

About #370, I'll see what I can do, but considering that I know almost
nothing yet of Genshi's internals, this may be too tall an order. I will
take the time to dive in, though.

-- Remy

signature.asc

Remy Blank

unread,
Apr 6, 2010, 5:09:10 PM4/6/10
to gen...@googlegroups.com, python...@googlegroups.com
Tim Hatch wrote:
> Twill did something like that and it's caused us a fair bit of hassle in
> testing because it bundled what are now 'old' versions of some modules.
> You get a different behavior as a user of twill if you 'import foo;
> import twill' vs 'import twill; import foo'.

Yeah, I don't like it either, but we had to start thinking about
possible options. The Trac use case may be a bit different, as it's
mostly Trac importing your module (plugin) and not the other way around,
so we more or less control the order. But still, not pretty.

Anyway, it seems that both Babel and Genshi are well on their way to get
new releases, so the point is hopefully moot.

-- Remy

signature.asc
Reply all
Reply to author
Forward
0 new messages