On Thu, Aug 28, 2008 at 02:25:30PM -0600, dann frazier wrote: > > - Full support, which currently noone wants to handle. > One plus for #4 is that it gives us the option of doing #5 later, in > case someone steps forward between now and the end of etch support.
Yes. > > I know its not really pretty, but for now its the best we can get IMHO. > > If we choose to migrate users within a stable release, we'd need to have > some predetermined overlap between lennynhalf availability and 2.6.18 > security support so we can communicate to users that, at some point in > the future, they will be asked to migrate and they'll have n months to > do so. > > We would also need a pretty good communication plan, that is ideally > in-band of the normal install/upgrade process. For example: > 1) 5.0r0: NEWS.Debian that warns of the shorter-than-normal security > support I also needs to be mentioned in the release notes, which anyone should read. NEWS.Debian is ignored often. > 2) 5.0+half: NEWS.Debian that gives a N month warning to migrate to > lennynhalf kernel I would use debconf. > 2) 5.0+half+N-months: NEWS.Debian that warns that they are installing > an unsupported package I would just replace it with a dummy package which fails in preinst, so it can never be configured, but will not remove the old data on upgrade. Bastian -- A little suffering is good for the soul. -- Kirk, "The Corbomite Maneuver", stardate 1514.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]