1 |
On Tuesday 08 November 2005 17:29, Brian Harring wrote: |
2 |
> On Sun, Nov 06, 2005 at 11:54:11AM +0900, Jason Stubbs wrote: |
3 |
> > On Sunday 06 November 2005 06:09, Brian Harring wrote: |
4 |
> > > Yes we'll run aground of the dead 2.1 release (not incredibly happy |
5 |
> > > about that), but I'd like to see if we can get bug fixes out a bit |
6 |
> > > quicker, with some semblence of a gurantee we're not tagging in stuff |
7 |
> > > an admin isn't going to care about. |
8 |
> > |
9 |
> > What sort of bug fixes are you looking to get out quicker? While the EAPI |
10 |
> > stuff drew out .53 a little longer than originally expected it was still |
11 |
> > only 30 days from first rc to final (assuming _rc7 is final). I can't |
12 |
> > really see the necessity for getting non-regression fixes out "quicker". |
13 |
> > At the moment, a lot of fixes go out all at once rather than in lots of |
14 |
> > small bumps. I doubt the overall speed would change very much. |
15 |
> |
16 |
> Question is how will it scale for non-bugfixes, disruptive changes |
17 |
> like cache backport, elog backporting, confcache, etc? What I'm |
18 |
> concerned about is what's going to occur with .5x when large changes |
19 |
> start sliding into it (or into a minor)- basically the territory we're |
20 |
> wandering into right now with cache/exec refactoring for .54. |
21 |
|
22 |
If the changes are reviewed roughly in proportion to the number of hunks, we |
23 |
should be okay. At minimum, we should at least see how .54 turns out as there |
24 |
will be a few major changes in there already. I kind of expect .54 to do |
25 |
better than .53 actually. |
26 |
|
27 |
Remember also that if we go the 2.1.x route, 2.0.x bugfixes can be pushed out |
28 |
quicker but the fixes all have to be committed twice. I for one am terrible |
29 |
at that. ;) |
30 |
|
31 |
-- |
32 |
Jason Stubbs |
33 |
-- |
34 |
gentoo-portage-dev@g.o mailing list |