➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eli.bendersky
Recipients barry, eli.bendersky, eric.smith, ethan.furman, ncoghlan, ned.deily, python-dev, serhiy.storchaka, vstinner
Date 2014-06-24.22:10:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda_MZ0s1jueKhgQh6OWoW+4c4ERYcY3yDgRW9nZ5yYBk+Q@mail.gmail.com>
In-reply-to <1403645356.15.0.700042734507.issue18780@psf.upfronthosting.co.za>
Content 
On Tue, Jun 24, 2014 at 2:29 PM, Ned Deily <report@bugs.python.org> wrote:

>
> Ned Deily added the comment:
>
> The 3.3 branch is now only open for security fixes so this issue doesn't
> appear to warrant backporting there.
>
> ----------
>

These questions keep popping up in various places, being asked even by core
devs like here.

Is there a place where this is described formally? I.e. 3.5 is trunk, 3.4
is bug fixes, 3.3 is security fixes, doc fixes good everywhere, and some
info about 2.7? I imagine since this only changes once per 18 months or so,
it should not be difficult to maintain and can just be part of the release
manager's job.
History
Date User Action Args
2014-06-24 22:10:04eli.benderskysetrecipients: + eli.bendersky, barry, ncoghlan, vstinner, eric.smith, ned.deily, ethan.furman, python-dev, serhiy.storchaka
2014-06-24 22:10:04eli.benderskylinkissue18780 messages
2014-06-24 22:10:04eli.benderskycreate