On Tuesday 24 February 2009 12:19:19 Patrick R. Michaud wrote: > I can definitely live with this. The only change I might > suggest is that we go ahead and call April 2009 the 1.3 release, > so that the July/".6 release" is the deprecation point > in 2009 as well. Or, we could skip from 1.3 (June) > to 1.6 (July). > > But it's not worth a debate over -- if others like it, great; > if not, then I'm great with the above plan.
Allison and I talked about that. It seems to me that we might as well put likely removal dates (in terms of "GONE BY AUGUST 2009") in our deprecation notices for the sake of clarity anyway, so we might as well keep our numbering scheme very boring and very predictable. That means we plan in biannual chunks (here are the features we want to provide in the next six months), we have a six month deprecation cycle (removing deprecations no sooner than six months), and we increment the major version number once a year. It's very boring and there's no magic, and I like both of those features very much. -- c _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
