[please keep cc'ing debian-boot, discover-workers and David Nusinow] Hi
I see 3 different ways how the transition from discover 1 to discover 2 in Debian could be handled. All of them need coordination between progeny (probably the maintainer of the new discover 2 packages) and debian-boot (maintainer of discover1 and heavily relying upon discover for debian-installer). As I and David are going to take over the maintainership of discover 1.5 we are interested in fixing the transition plan now. 1. Alternative: This is basically branden's proposal, see this mail[1] for more details a) rename discover to discover1 b) upload discover 2 as discover (with all the debs and udebs) c) drop discover1 when discover (2) provides all the features we need and works well 2. Alternative: This is the oposite of 1): a) upload discover 2 as discover2 (with all the udebs and debs) b) drop discover (1.5) when discover2 provides all the features we need and works well c) rename discover2 to discover 3. Alternative: This is a variant of the 2. alternative which allows the d-i team to move to discover 2 while not affecting normal discover users. Step a) could also be done by the d-i team independently of progeny. a) upload discover2 packages as discover2 with only the udebs b) upload discover2 as discover (with all the debs and udebs) when discover2 provides all the features we need and works well I personally prefer Alternative 2 or 3 (especially if progeny does not upload discover2 packages until the end of the year), but I'm open for suggestions and can live with every of the three variants. One other possibility I see is the introduction of a dummy package discover to ease the transition. But I'm not sure if won't make things more complicated as necessary. What do you think about it? Gaudenz [1]http://lists.debian.org/debian-boot/2003/debian-boot-200312/msg00159.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
