On Tue, 2006-04-18 at 17:54 -0400, Jeff Spaleta wrote: > On 4/17/06, Jeremy Katz <katzj@xxxxxxxxxx> wrote: > > Comments, feedback, etc? > > Anyway we can have some restrictions on how late in the cycle items > get punted out of Core? Or atleast some restrictions on the minimum > amount of notice Extras maintainers are given with regard to the > intent to punt something out of Core and some guidance as to what > constitutes appropriate notice, so we can avoid a scramble to reimport > something into Extras after it is dropped from Core. Personally, I think this falls (largely) into the category of feature freeze. Calling out "end of new module/module removal" makes sense. Granted, if we're 200k over the size of a CD, we'll probably end up making the call of remove something, but those should be exception cases that we wave our hands wildly about, and not the norm. > I'd like to be in a position where Extras maintainers can reasonable > have enough time to get a soon to be dropped Core library through > Extras review and in Extras cvs an ready to fire off a build as soon > as its dropped from Core. This isn't the sort of thing Extras can > dictate to Core, Core needs to have some established guidance to make > sure this sort of thing gets communicated in a way that Extras > maintainers are not caught with their pants down with 2 weeks before > final release. In general, I'm trying to get a little bit of better notification in place for handling of the Core/Extras divide by delegating the addition of some steps to the process ;) Jeremy
