On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner victor.stinner@gmail.comwrote:

Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right?

Typically we do one last release before shutting the last bugfix branch down, but that's Georg's call since 3.3.5 was released so recently.

-Brett

Victor Le 17 mars 2014 07:48, "Larry Hastings" larry@hastings.org a écrit :

...

The "3.4" branch is now checked in. It contains all the 3.4 releases since 3.4.0rc1. Its current state is effectively 3.4.1.

The "default" branch is now 3.5.

Cry havoc, and let slip the dogs of war,

*/arry*

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Am 17.03.14 16:18, schrieb Benjamin Peterson:

On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote:

...

On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner victor.stinner@gmail.comwrote:

...

Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right?

Typically we do one last release before shutting the last bugfix branch down, but that's Georg's call since 3.3.5 was released so recently.

Given that, I propose 3.3 goes into security fix mode immediately.

+1

Martin

On 3/17/2014 11:18 AM, Benjamin Peterson wrote:

On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote:

...

On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner victor.stinner@gmail.comwrote:

...

Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right?

Typically we do one last release before shutting the last bugfix branch down, but that's Georg's call since 3.3.5 was released so recently.

Given that, I propose 3.3 goes into security fix mode immediately.

Traditionally, the final maintenance release has been either simultaneous or a week after the next version. Having 3 active 3.x branches on top of 2.x is a burden. I also think a week before is fine.

Terry

On 3/17/2014 11:42 AM, Jesus Cea wrote:

On 17/03/14 09:51, Victor Stinner wrote:

...

Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right?

Tradition says that until release *.1 is published. That is, 3.4.1 in this case.

According to my memory, bug fixing traditionally stopped with the next x.y.0 release (but which was not called .0)

But release manager will tell.

Having multiple branches under maintenance severely affect all committers.

Terry

On 18 Mar 2014 07:37, "Victor Stinner" victor.stinner@gmail.com wrote:

Hi,

I modified the Misc/NEWS file:

• I moved 3.3 sections to Misc/HISTORY: items were already present, but the format in Misc/NEWS was improved (changeset 6ba468d4fa96)
• I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be present in the 3.4 branch (changeset cb161cd94e6e)

Is that correct?

Not everything was cherry picked, so we'll need to review that to move the 3.4.1 fixes back to the appropriate section.

Cheers, Nick.

Victor

2014-03-17 7:38 GMT+01:00 Larry Hastings larry@hastings.org:

...

The "3.4" branch is now checked in. It contains all the 3.4 releases

since

...

3.4.0rc1. Its current state is effectively 3.4.1.

The "default" branch is now 3.5.

Cry havoc, and let slip the dogs of war,

/arry

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Am 17.03.2014 22:36, schrieb Victor Stinner:

Hi,

I modified the Misc/NEWS file:

• I moved 3.3 sections to Misc/HISTORY: items were already present, but the format in Misc/NEWS was improved (changeset 6ba468d4fa96)
• I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be present in the 3.4 branch (changeset cb161cd94e6e)

Is that correct?

The changes not merged in 3.4.0 will all be in 3.5.0; please reinstate the NEWS entries under the 3.5 heading.

Georg