Release-Notes for Potato - Information and Help Needed

1999-05-13 Thread Bob Hilliard
[Please, no replies to this list!]

 I am starting to compile information for the Release-Notes for
potato.  All developers are requested to forward information about
significant changes in packages or installation/upgrading tools to
[EMAIL PROTECTED]  

 Basically, what is needed is anything that will make the users'
life a little easier when she upgrades to or installs potato.  Julian
Gilbey <[EMAIL PROTECTED]> has suggested the following cases as a
guide to the type of information that is required:

 The "before" cases:

 - If the user doesn't read the upgrade notes for this package
   *before* upgrading, his/her system will die a horrible death or
   will lose major functionality
 => should appear on main release notes page, and the situation
should be improved if this is at all possible
   [possible egs: kernel-2.2 (utmp group etc), great X re-org]

 - If the user doesn't read the upgrade notes for this package
   *before* upgrading, the upgrade will not run smoothly
 => the maintainer needs to clean up their package so this is not
the case, but if this is impossible, the situation should be
described on the main release notes page

The "after" cases:

 - If the user doesn't read the upgrade notes for this package
   *after* upgrading, his/her system will die a horrible death or
   will lose major functionality
 => should appear on main release notes page, and the situation
should be improved in whatever way possible

 - If the user doesn't read the upgrade notes for this package
   *after* upgrading, the package concerned will lose significant
   functionality, or the sysadmin's configuration will have been lost,
   or similar
 => should appear in a list on the release notes page.  These
could link to text describing the problems, or the page could
just say "The following packages have major changes which will
most likely require manual intervention after the upgrade.
It is recommended that you read
/usr/doc//README.Debian_upgrading after installing
any of these packages to ensure a smooth upgrade."

 I would rather receive too much information than too little.  I
will edit submitted material as needed to avoid letting the document
grow too much.

 I do not consider myself sufficiently knowledgeable about all
aspects of Debian to do justice to the Release-Notes, and I don't
really have the time to do it properly.  If anyone is willing to
adopt this project please email me or Adam Di Carlo
<[EMAIL PROTECTED]>, and I will happily turn it over to you. 

Bob
-- 
   _
  |_)  _  |_   Robert D. Hilliard<[EMAIL PROTECTED]>
  |_) (_) |_)  Palm City, FL  USAPGP Key ID: A8E40EB9



Release Plans (19990513)

1999-05-13 Thread Richard Braakman
(Please send followups to this mail to debian-devel, not debian-devel-announce)

This is what I learned from the responses to the previous announcement.


  Boot disks:
Creating disk sets with the much larger 2.2 kernels is proving difficult.
This is likely to delay the freeze unless the boot-floppies team gets
some help.

  CD Images:
The tools that create the CD images could use some fixing.  Join the
debian-cd list if you wish to help.

  Architectures:
PowerPC will also release with potato.  That makes the full list:
  i386 m68k alpha sparc powerpc

  PAM:
Ben Collins sponsored full pamification as a release goal.  The main
packages that need work are the shadow suite, and xdm.

 Perl 5.005:
Two people volunteered as coordinator for this, and promptly got
into an argument :-)  I'll pick "wait and see" on this one.

Richard Braakman