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

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

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

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4