Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: stabilizing expat 2.0.0
Date: Thu, 17 May 2007 08:01:00
Message-Id: pan.2007.05.17.07.57.00@cox.net
In Reply to: Re: [gentoo-dev] Re: stabilizing expat 2.0.0 by Caleb Tennis
1 "Caleb Tennis" <caleb@g.o> posted
2 35060.192.168.2.155.1179337715.squirrel@××××××××××××.com, excerpted below,
3 on Wed, 16 May 2007 13:48:35 -0400:
4
5 > I have no problem waiting for 2007.1, if Gnome and KDE don't mind. I
6 > don't know what hackery has to take place to do that, but I'm sure
7 > someone out there does.
8
9 What sort of timing are we looking at for 2007.1 anyway? With .0 delayed
10 as it was, is .1 going to be relatively quick, say August, or are we
11 looking at November now?
12
13 If it's August, there shouldn't be much KDE to upgrade, maybe stabilize
14 3.5.6. 4.0 is the big one, but that's tentatively timed for Sept. if I'm
15 not mistaken, and if release dates don't slip. If 2007.1 is November,
16 there's a slim chance of getting 4.0 in, but not if it's like 3.5 was
17 (IIRC 3.5.0 and 3.5.1 never stabilized, it was 3.5.2 before the issues
18 were worked out enough to stabilize, which would put bump stable KDE
19 4.0.x to 2008.0 at the earliest).
20
21 I doubt anyone wants to wait for a a November expat-2 stabilization,
22 however, so if 2007.1's going to be that long, unless we want to talk
23 about 2007.0-r1 and I doubt anyone's up for that either, the timing just
24 doesn't look like it's going to work for a release/profile timed expat-2
25 stabilization. It'd be nice, but...
26
27 So what /does/ the timing look like for 2007.1?
28
29 --
30 Duncan - List replies preferred. No HTML msgs.
31 "Every nonfree program has a lord, a master --
32 and if you use the program, he is your master." Richard Stallman
33
34 --
35 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Re: stabilizing expat 2.0.0 Rumen Yotov <rumen@××××××.org>
Re: [gentoo-dev] Re: stabilizing expat 2.0.0 Chris Gianelloni <wolf31o2@g.o>