On Wed, Apr 11, 2007 at 10:34:47AM +0900, Charles Plessy wrote: > I propose another idea: having a major.minor release scheme in > which we guarantee the upgrade path from major.x to major+1.0, and > from one minor release to the other. One big obstacle common to all > these directions is to find a security strategy which would not drain > all the workforce of the Project. Isn't that essentially the same idea as http://kitenet.net/~joey/code/debian/cut/ with a mapping between "major.x" and "cut x" ? (I think it is the same thing in effect, and I'm really hoping we can make that happen; somewhat interested in discussing any differences though) Cheers, aj
Attachment:
signature.asc
Description: Digital signature