Jim Pick <jim@jimpick.com> writes: > > We already have a release manual, to put it short: > > > > 1/ Identify all the critical bugs (cf the bug tracking system for the > > definition of 'critical') > > 2/ Fix them and upload the corrected packages. > > 3/ Check the problems are gone. > > 4/ Release the distribution. > The release manual I am going to write tomorrow will probably be over > 20 pages long. It's exactly the same thing as what you wrote down, except > that it defines the tasks in detail, milestones, manpower requirements, > contingencies, 'pass' criteria, etc. > space shuttle mission, but it is a complex thing that requires coordinating > 200+ developers. please keep in mind that your product must be read by *all* developers -> each page is read by 200 people, in this time they can't work on the release. You slowdown the release process by writing long documents. Please keep it short. Everything that's longer than two A4 pages (140 lines) isn't acceptable for the Debian release process! Please don't try to increase the bureaucracy of Debian. IMHO it's very easy to write 100 pages. But it's more difficult to express the same thing on 1 page. Please work in this direction. Thanks. And keep in mind that the work you propose must be done by *volunteers*. The main focus shouldn't be the time line, because people can't be forced to do something. Instead you should try to make individuals responsible for each single task. Responsible doesn't mean that the person must do the work, instead he must try to coordinate the process. At the moment I would say that Richard Brackmann is responsible for the migration process from libc5 to libc6, because he post regularly the status and shows the difficulties that needs to be solved. Other aspects, like the PAM, needs a coordinator, too. Bye Christian -- Christian Leutloff, Aachen, Germany leutloff@sundancer.oche.de http://www.oche.de/~leutloff/ Debian GNU/Linux 1.3.1! Mehr unter http://www.de.debian.org/
Attachment:
pgpYBhBoRsF1Q.pgp
Description: PGP signature