1 |
On Thu, 06 Apr 2006 19:11:49 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
|
4 |
> The manifest code doesn't have very many use cases so I'd expect that |
5 |
> we would have hit most major problems by now (even with a small |
6 |
> sample). Any necessary changes are likely to be small patches. As |
7 |
> an alternative, we can cut the 2.1 branch at the point before |
8 |
> manifest2 was merged (2.1_pre7, essentially). |
9 |
|
10 |
Releasing 2.1 without manifest2 is a no go, it would significantly |
11 |
delay the deployment and transition. I'm not requesting to delay 2.1 |
12 |
for another few months, just one more pre release so people get a |
13 |
chance to test it for one or two weeks. |
14 |
|
15 |
> > The remaining feature I'd like to get into 2.1 is the |
16 |
> > tree-format-check issue, but that could probably be slipped in in |
17 |
> > the rc phase (don't really like that idea, but it's an option). |
18 |
> |
19 |
> I don't want to rush the development of new features such as |
20 |
> manifest2 or the tree-format-check. We have a 2.1 branch that, in |
21 |
> it's current state (2.1_pre7-r4, for example), provides significant |
22 |
> benefits over the 2.0.x branch. By delaying 2.1's release for the |
23 |
> addition of _new_ features, we run the risk of the release being |
24 |
> delayed indefinitely by "just one more feature" syndrome. |
25 |
> Personally, I'd rather have shorter release periods so that "just one |
26 |
> more feature" syndrome becomes less of an issue. |
27 |
|
28 |
Ehm, this is not "just one more feature", both manifest2 and |
29 |
the tree-format-check are things to improve forward compability (or for |
30 |
the latter even enable forward compability at all), so delaying them |
31 |
will hinder future development, not only for us. |
32 |
Also this isn't exactly news to you all as I sent my intentions already |
33 |
a while ago, and last I asked you all agreed with them, so is there any |
34 |
reason to rush this now? |
35 |
|
36 |
Marius |
37 |
-- |
38 |
gentoo-portage-dev@g.o mailing list |