default hg.python.org/cpython is now 3.5
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/
Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right?
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
On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner <victor.stinner@gmail.com>wrote:
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
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.com>wrote:
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.
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.com>wrote:
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
Am 17.03.2014 17:37, schrieb "Martin v. Löwis":
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.com>wrote:
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
I agree. I would have released 3.3.5 after 3.4.0, but since 3.3.5 came along *and* took a second rc, it fills the function nicely.
I will make an exception if a regression in 3.3.5 is discovered soon-ish.
Georg
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.com>wrote:
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 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.
But release manager will tell.
-- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
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
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?
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
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
On 03/17/2014 04:23 PM, Nick Coghlan wrote:
On 18 Mar 2014 07:37, "Victor Stinner" <victor.stinner@gmail.com <mailto: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.
I merged "default" into "3.4" (3a3a83195159), so every change that was in "default" last night will automatically go into 3.4.1. Stuff that got cherry-picked back for 3.4.0 should already be in their correct sections.
I worked pretty hard to get that right, so while I'd be interested to hear if I got it wrong, my assumption (my hope) for now is that Misc/NEWS is basically correct in both "3.4" and "default".
//arry/
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
Hi,
2014-03-18 7:19 GMT+01:00 Georg Brandl <g.brandl@gmx.net>:
Am 17.03.2014 22:36, schrieb Victor Stinner:
I modified the Misc/NEWS file: (...) 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.
Oh ok, I didn't notice that 3.4.1rc1 items were all missing from 3.5. Does it look better with the following changeset? http://hg.python.org/cpython/rev/b7f2b1bd49f3
I compared Misc/NEWS with Misc/NEWS of 3.4 branch: the only change is the 2 new changes specific to 3.5.
Victor
participants (9)
-
"Martin v. Löwis" -
Benjamin Peterson -
Brett Cannon -
Georg Brandl -
Jesus Cea -
Larry Hastings -
Nick Coghlan -
Terry Reedy -
Victor Stinner