On Tue, Feb 24, 2009 at 6:23 PM, Andy Lester <[email protected]> wrote: > > On Feb 24, 2009, at 5:21 PM, chromatic wrote: > >> Anybody willing to argue timezone ambiguity when discussing the exact >> moment >> of deprecated feature removal needs a much better hobby than filing bug >> reports and writing angry screeds on a mailing list. I suggest going >> outside. > > > Oh, sure, I'm not seriously suggesting that we need a timestamp. I just > bring up the time because deadlines w/o times is a pet peeve of mine. > > But I DO think that "August 2009" isn't specific enough. If you mean "end > of August 2009", then just say that. > > xoa
We don't mean, that, though: we mean that it might go away in a particular upcoming release. And we may not have a chance to, or we might change our minds. I just updated DEPRECATED.pod to tag the ones eligible for removal before 1.0 as [BEFORE 1.0]; the few that were added already as [post 1.3] I updated to be: [eligible in 1.4] That, is, those items are eligible for removal in that release; If we don't remove them in that release, then we'll update the file just before the 1.4 release to say [eligible in 2.0]. When we're about to cut 1.0, we can change the remaining [BEFORE 1.0] items to be [eligible in 1.4]. Hope that works for folks. Regards. -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
