Re: LVM 1.0 release decision

[Jeff Garzik <jgarzik@mandrakesoft.com>]

"Heinz J. Mauelshagen" wrote:
> In order to avoid this difference we provide smaller patches more often now.
> We have started already with a subset of about 50 necessary patches.
> 
> Even though we get kind support from Alan Cox to get those QAed and integrated,
> the pure amount of patches will take at least a couple of weeks to make it in.

Are you sending them all in one batch (50 e-mails to Linus at once), or
trickling them to Linus a few at a time?  It might be faster to send him
a batch (though not necessarily 50), noting with each e-mail, after each
patch's description, that the particular patch depends patches C, F, and
H that have come before it.  That way Linus can apply 8 out of 10
patches, and then you synchronize with him and start the cycle over
again.


> In regard to this situation we'ld like to know about your oppinion on
> the following request:
> is it acceptable to release 1.0 soon *before* all patches to reach the 1.0 code
> status are in vanilla (presumed that we provide them with our release as we
> always did before)?

Subsystems are often maintained outside the Linus tree, with code
getting pushed (hopefully regularly) to Linus.  For such scenarios, it
should be no problem to release software before all of it passes Linus. 
You are the one who has to deal with user support after all :)   Just
make sure that all fixes and changes currently in the kernel are also in
your software release...

	Jeff


-- 
Jeff Garzik      | Game called on account of naked chick
Building 1024    |
MandrakeSoft     |