[gentoo-dev] What should be in place before 1.0 release

[Karl Trygve Kalleberg <karltk@prosalg.no>]

Hi gang.

I just like to voice my opinion about issues that should be addressed
before the release of Gentoo Linux 1.0 (hurrah!)

While I can to a large degree accept that the distro itself is technically
ready enough to be released, our development team is in no way prepared to
handle the influx of new users.

At minimum, we should have the following points fixed:
1) A proper bug-reporting system. We simply won't be able to keep track of
the issues cropping up in gentoo-{dev,users,ebuild,whatever} given the
current developer situation.
2) A flawless installation guide. This means that we should do the
installation of the 1.0 version in a handful of different configurations
and make certain the installation guide is not only correct, but succinct
and unambiguous. This is tricky, but every hour we spend fixing it before
final release, will save us tenfold down the line.
3) Verify that all our ebuilds actually work as advertised. Some ebuilds
seem to be more error-prone than others (minicom, koffice). The ones that
have any problems whatsoever should be masked out until we know that they
really work.
4) In a related note, we should have a
"grace-period"/"codeslush"/"codefreeze" of at least one week where we do
not add new stuff, and do nothing but bug-squashing. We should verify that
*all* ebuilds have been tested, preferrably with *all* their optional USE
arguments.
5) We should have a release plan on the web, a task-list if you will,
where we check off items as we progress along to 1.0. This will hopefully
work as a great motivator once we're over half-way ;)
6) We should officially nominate a Release Manager (I guess this will be
drobbins, but it would be nice for everybody, including non-developers, ie
hardcore Gentoo testers to know who's neck is on the block ;).
7) Perhaps we even should have a release team that acted as drobbins'
elven helpers and make certain that all the items on the task-list are
addressed in a timely fashion. Perhaps all the developers should just act
as elven helpers.. 

Hope this sets thoughts churning. If we want 1.0 to be stable and good, we
will have to put a lot of effort into it, and do so in a structured
fashion. The all-nighter "throw code at it until it works" is NOT an
option. 


Kind regards,

Karl T