2012/6/28 Jesus Cea <j...@jcea.es>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Python 3.3 is currently in beta, so the rythm of new patches in > "default" will decrease and people with new features MUST wait until > 3.3 is out. I think this is a waste of time. And even if people is > working with HG private clones, they can't test using the buildbots > neither mark a bug as fixed in the tracker. > > If we create a new 3.3 branch *NOW* and add it to the buildbots, > people can keep working in "default" full speed (for 3.4), while 3.3 > branch is getting ready for general release. We only need to remember > to appy the same rule current rule: any patch in branch "x" must be > "merged" into branch "x+1" too. > > Has this step been considered?. I think it is a nice improvement that > HG enables and we are not using. > > What do you think?.
I, for one, had my fill of maintaining 4 branches when we were doing two versions of 2.x and two versions of 3.x. People are free to put their features in their own private clones and await 3.4 development beginning. -- Regards, Benjamin _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
