1 |
On Mon, 2005-11-07 at 17:57 +0100, Gregorio Guidi wrote: |
2 |
> On Monday 07 November 2005 15:27, Chris Gianelloni wrote: |
3 |
> > ... |
4 |
> > > Hmm, I'd like it, if we also (re)moved stage1 and stage2 from visible |
5 |
> > > directory, and renamed stage3 to something more appropriate by the |
6 |
> > > 2006.0. I mean, it will probably be confusing for a new user if the |
7 |
> > > guide just says "Oh, we have this things that say 1 and 2 in the |
8 |
> > > directory, but please ignore them and start from 3, because 1 and 2 are |
9 |
> > > only for devs, k?" And it won't help, that old users will most likely |
10 |
> > > continue to advice for stage 1 in so many support channels. |
11 |
> > |
12 |
> > I'm not sure if the removal of stages 1 and 2 will happen in time for |
13 |
> > 2006.0, simply because it is a *very* heated issue and one that will |
14 |
> > take some serious politics to get enacted. |
15 |
> > |
16 |
> > I guarantee that I won't be a popular guy. *grin* |
17 |
> |
18 |
> That's where a bit of PR and marketing techniques could help... if you say |
19 |
> "Release Engeneering decided to not release stage1 and stage2 for 2006.0." |
20 |
> every user out there will try to kill you. |
21 |
> Instead, if you announce "For 2006.0, Release Engeneering decided to unify the |
22 |
> functionalities of the three installation stages you were used to in single |
23 |
> Stage file that provides the same capabilities and flexibility with less |
24 |
> complication." (and change the handbook along this direction) how can someone |
25 |
> complain about that? |
26 |
|
27 |
Doing a bootstrap from a stage3 tarball is worthless. You've made it |
28 |
sound like users should bootstrap from a stage3 tarball. |
29 |
|
30 |
While I completely agree that it is all in how you present it, there are |
31 |
certain things that we absolutely wish to get away from, and one of them |
32 |
is having the user *ever* run bootstrap.sh themselves. |
33 |
|
34 |
> It's just a matter of using the right words ;) |
35 |
|
36 |
-- |
37 |
Chris Gianelloni |
38 |
Release Engineering - Strategic Lead |
39 |
x86 Architecture Team |
40 |
Games - Developer |
41 |
Gentoo Linux |