Gaudenz Steinlin wrote: > Well, here's what I'd personally like: :) > > 1) Get a good feedback cycle going between Progeny and debian-boot > regarding discover2's suitability for debian-installer. The goal > here is "feature-complete", not "bug-free". > 2) Hand off maintenance off Discover 1.x to the d-i team. You guys are > already the de facto maintainers of Discover 1.x and everyone who > reads the changelogs knows that. > 3) Rename the current discover source package to discover-old or > discover1; drop the libdiscover-dev package from it; rename the > discover package to discover-old or discover1, and have it Conflict: > discover. > 4) Thanks to 1), we will upload discover 2.0 to Debian unstable. > > That should make it clear that DIscover 1.x is deprecated, but will > enable either to be installable, and d-i can use either one, > transitioning on a schedule that is completely under your control. > > How does that sound? Sounds reasonable. > IMO if we want to release sarge with discover2 for d-i we have to > release beta2 with discover2 (after that it's too late for this change!) This is actually the kind of thing I would prefer to hold out of beta 2, and look at adding, along with any other changes to very core parts of the system, until just after. If it goes it beta 2 it will either get two weeks of testing, max, before beta, or the beta schedule will slip. It's better to keep the betas coming out on a good schedule. It also has the potential to make life for porters very hard, and I would really like to see another port be released with beta 2. -- see shy jo
Attachment:
signature.asc
Description: Digital signature