[Python-Dev] Python 2.3 patch cut-off date
Martin v. Loewis
09 May 2002 15:50:33 +0200
Jason Tishler <firstname.lastname@example.org> writes:
> I would rather have clearly stated deadlines that are subject to change
> (i.e., slippage). In this way, volunteers can better plan their time.
> Can I play with my daughter now or should I submit a patch? Can I go
> to sleep now or should I submit a patch? Etc.
In any schedule, there likely would be a month between a1 and a2, so
the release of Python 2.3a1 would simultaneously be a last call for
great new features. Between a1 and c1, there would be four months,
giving plenty of time (IMO) for bug fixes.
Anything that takes more time then four months is complex enough to
wait for 2.4 to mature. There will be always a next release.