[Python-Dev] Re: Stability and change

Anthony Baxter Anthony Baxter <anthony@interlink.com.au>
Mon, 08 Apr 2002 22:25:23 +1000

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

You're not the only one :)

> > Who?  Anthony Baxter withdrew from the 2.1.x line after 2.1.2 -- he was
> > tired of doing it.
> I'm reasonbly likely to disappear for a bit after 2.2.1 is done.
> Doing a maintence release is a lot of work, and it's dull, tedious
> work (but not thankless!).

I can probably step back in for a bit while Michael steps back. After
2.1.2, the conference and then moving house, I didn't have the time 
(or the net connection) to keep this going. Michael's done an amazing
job on 2.2.1, and I'm so glad he stepped in.

However, it's pretty clear to me that trying to keep doing the patch
monkey role for multiple releases in a row is a great way to burn out 

> I'm reasonably willing to do 222 so long as it's not for a few months.

The key thing, I think, is to keep on top of the backporting. If it 
slips, it's an absolute monster to catch up.
> > 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.

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

> > Isn't this dangerous?  Build config seems very delicate to me.
> Bloody hell yes.

<aol>me too</aol>. I know I try to build releases on everything I can
get hold of (the cf.sf.net machines, the dec^Wdigital^Wcompaq^Wwhoever
testdrive boxes), but that's a whole lot of work. And that's not including
the, ahem, less unixish Unixes like AIX and HP/UX. Unless it's a platform
to which I have a lot of exposure (and in the last few years that's been
mostly linux and solaris), I'm not going to try and make this stuff work.
> This is a real issue.  There are build fixes for AIX 3 on sf for 221;
> they're not going in because I'm scared that they'll break something
> else.

*nod* Yep. The chances of a build fix going in that's not completely
and utterly clearly the Right Thing to do is almost nil. And given that
the number of people who are actually willing to _test_ builds (as 
opposed to just bitch about how it doesn't do exactly what they want)
is almost nil, I can't see this changing. 
more later,
Anthony Baxter     <anthony@interlink.com.au>   
It's never too late to have a happy childhood.