RetroSearch Browse

Tue Aug 28 07:11:05 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-August/121474.html

On 28.08.2012 06:22, Petri Lehtinen wrote:
> Georg Brandl wrote:
>> 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.
>
> Where should I put the news entry for fixes that will go to 3.3.1? The
> top item in Misc/NEWS is 3.3.0 RC 2. The stuff in your private clone
> will be released as 3.3.0, so can a 3.3.1 entry be added to the
> default branch of the public repo now?

Yes.

> And if changes like this are added now, they will be included in 3.2.4
> but not in 3.3.0. Is this bad?

Sounds fine to me.

Georg

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

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

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