Ptyon 2.3.5 probably coming in January;get your bugs/patches reported!

[Brett C.]

Anthony Baxter, our ever-diligent release manager, mentioned this past week
that Python 2.3.5 will most likely come to fruition some time in January (this
is not guaranteed date). This means that in order to have enough time to
proper evaluate new patches and bugs they must be reported **now**! A one
month lead time is necessary to properly look at, test, and commit patches, let
alone coming up with solutions to any reported bugs.

Please realize, though, that reporting a bug or submitting a patch now does not
guarantee that it will committed in time! The free time of the development
team is limited. If you want to help a bug or patch along to make it easier to
be evaluated and thus raise its chances of being dealt with please see the
"Helping Out" section of the 'Intro to Development' essay at
http://www.python.org/dev/dev_intro.html .

As always, both bugs and patches should be reported to Python's SourceForge
tracker at http://sourceforge.net/bugs/?group_id=5470 and
http://sourceforge.net/patch/?group_id=5470, respectively.

-Brett Cannon

[Roy Smith]

In article <ma**************************************@python.o rg>,
"Brett C." <ba*@OCF.Berkeley.EDU> wrote:

Anthony Baxter, our ever-diligent release manager, mentioned this past week
that Python 2.3.5 will most likely come to fruition some time in January
(this is not guaranteed date).

Interesting. Does that mean that 2.3 and 2.4 will be maintained in
parallel for a while? That would be awesome.

[Aahz]

In article <ro***********************@reader1.panix.com>,
Roy Smith <ro*@panix.com> wrote:

In article <ma**************************************@python.o rg>,
"Brett C." <ba*@OCF.Berkeley.EDU> wrote:

Anthony Baxter, our ever-diligent release manager, mentioned this
past week that Python 2.3.5 will most likely come to fruition some
time in January (this is not guaranteed date).

Interesting. Does that mean that 2.3 and 2.4 will be maintained in
parallel for a while? That would be awesome.

Depends what you mean by "in parallel". This is no different from what
occurred during the transition from 2.1 to 2.2 and 2.2 to 2.3; we're
just getting steadily more methodical about it.
--
Aahz (aa**@pythoncraft.com) <*> http://www.pythoncraft.com/

WiFi is the SCSI of the 21st Century -- there are fundamental technical
reasons for sacrificing a goat. (with no apologies to John Woods)

[Tim Peters]

[Brett C]

Anthony Baxter, our ever-diligent release manager, mentioned this past week
that Python 2.3.5 will most likely come to fruition some time in January
(this is not guaranteed date).

[Roy Smith] Interesting. Does that mean that 2.3 and 2.4 will be maintained in
parallel for a while? That would be awesome.

They'll be maintained in parallel through 2.3.5 in January, which is
all Brett said. If history is a guide, after 2.3.5 nobody will
volunteer to work on a 2.3.6, and 2.3.5 will be the last release in
the 2.3 line. It's *possible* that volunteers for 2.3.6 will appear.
That would be unprecedented, but not impossible ...