RetroSearch Browse

Sun Aug 26 22:56:18 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-August/121466.html

On 26.08.2012 21:15, Chris Jerdonek wrote:
> Now that the 3.3 release clone has been created, can someone clarify
> what changes are allowed to go into the default branch?  Is it the
> same policy as if the changes were going into the release clone
> directly (i.e. code freeze unless you have Georg's approval), or are
> future changes for 3.3.1 okay, or is the default branch for changes
> that would go into 3.4?  If the policy is the same, when and how do we
> anticipate changing things for the default branch?

Changes to the default branch must be bugfix-only.  The 3.4 development
only opens when the 3.3 branch is created, which happens after the
release of 3.3.0 final.

Changes made in default and not cherry-picked to the 3.3.0 release clone
will therefore end up in 3.3.1 and 3.4.

cheers,
Georg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-August/121466.html below:

[Python-Dev] question re: default branch and release clone