Bugfix releases (RE: profiler results for __getattr__, am I reading this correctly ? )
richard at bizarsoftware.com.au
Fri Oct 19 01:33:22 CEST 2001
On Thursday 18 October 2001 17:58, Anthony Baxter wrote:
> >>> "Tim Peters" wrote
> > The bugfix release process is the topic of Aahz's PEP 6, who may have
> > believed that titling it "Bug Fix Releases" was enough clue <wink>:
> Ah, that cunning "hidden in plain sight" approach. Who'd have thought.
> It still doesn't cover the process of deciding what would go in the
> patch release... I know that I'd be happier upgrading to 2.1.2 than
> 2.2 in the next couple of months - and given the peasants-are-revolting
> sentiment of c.l.py at the moment, I doubt I'm the only one...
> How would this sound as a first cut at a what-goes-in-and-what-stays:
> a) bugfixes.
> b) no new modules, no new packages.
> c) no new methods on classes, unless they're bugfixes.
> d) if the bug fix relies on some 2.2-ism, then it's either rewritten,
> or ignored and relnoted
This looks like a good list - avoiding the stepwise changes, which have a
good chance of introducing new bugs.
More information about the Python-list