[Python-Dev] question re: default branch and release clone (original) (raw)
Chris Jerdonek chris.jerdonek at gmail.com
Sun Aug 26 21:15:04 CEST 2012
- Previous message: [Python-Dev] [RELEASED] Python 3.3.0 release candidate 1
- Next message: [Python-Dev] question re: default branch and release clone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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?
Thanks, --Chris
- Previous message: [Python-Dev] [RELEASED] Python 3.3.0 release candidate 1
- Next message: [Python-Dev] question re: default branch and release clone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]