[python-committers] 3.2 -> 3.3 merge pending? (original) (raw)
R. David Murray rdmurray at bitdance.com
Wed May 29 16:41:04 CEST 2013
- Previous message: [python-committers] 3.2 -> 3.3 merge pending?
- Next message: [python-committers] 3.2 -> 3.3 merge pending?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 29 May 2013 06:11:51 -0700, Senthil Kumaran <senthil at uthcode.com> wrote:
Is there a merge pending from 3.2 to 3.3?
http://hg.python.org/cpython/graph/83973?revcount=240 shows that last 3.2 change occurred 10 days ago and the branch has not been merged into 3.3 yet. http://hg.python.org/cpython/rev/b9b521efeba3?revcount=240 Is it pending intentionally or this should be merged and then we go forward with our business as usual.
I asked about this on IRC and was told that 3.2 is now a standalone branch like 2.7. Security fixes will be applied by the release manager only, and Georg doesn't see any point in null merging the commits.
--David
- Previous message: [python-committers] 3.2 -> 3.3 merge pending?
- Next message: [python-committers] 3.2 -> 3.3 merge pending?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]