[Python-Dev] Re: Stability and change

Jeremy Hylton jeremy@alum.mit.edu
Mon, 08 Apr 2002 14:12:39 -0400 (EDT)

>>>>> "AB" == Anthony Baxter <anthony@interlink.com.au> writes:

  >>>> Michael Hudson wrote
  >> I'm only scanning this huge thread, so I may be out of
  >> context/repetitive.

  AB> You're not the only one :)

I'm actually reading the whole thread, but I've only read 45% of the
messages that arrived before 2:40 p.m.  :-)

  AB> The key thing, I think, is to keep on top of the backporting. If
  AB> it slips, it's an absolute monster to catch up.

If we are going to change anything about the way we work, this strikes
me as the most likely candidate.  If we are going to continue to
maintain 2.1, then a developer who checks in a fix for some bug on the
trunk should also fix it for 2.2 and 2.1 if possible.

Basically, we need unambigious rules about when we'll stop doing micro
releases from a particular branch.  I think we should maintaince on
2.1 and 2.2, largely because 2.2 has so much experimental stuff.
Once we get to 2.3, we can re-evaluate the situation and decide
whether we want to continue maintaining 2.1.


  >> > I have a real problem when a group of people demands something
  >> > but won't volunteer anything to make it happen except their
  >> > complaints;

  >> Indeed; they can fuck off, in my book.

  AB> Absolutely. I believe the phrase "Go Stick Your Head In A Pig"
  AB> is also appropriate.

  >> > Isn't this dangerous?

I find it funny that Michael's asked the question before you wrote
your email.  I'm glad the time machine gets used for jokes now and