Le mercredi 02 février 2011 à 18:26 +0100, Jesus Cea a écrit : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/02/11 17:47, Barry Warsaw wrote: > > This is one of the primary problems solved by a dvcs. You can *always* and > > *easily* work on new features, publish them for comment and review by > > others, > > make continual progress regardless of the release status of the official > > branches, and easily track movement in those official branches. > > That being true, I am interested in the buildbots. Publishing a private > repository is not helpful, if you can't use the buildbots. > > I guess the best workflow would be for the Release Manager to create a > clone, keeping the development repository open while the RM checks the > clone and "cherry pick" changesets from the development branch if needed.
That sounds like a full-time job for the poor Release Manager. We really need to merge changesets *ourselves*. It is irresponsible to expect someone else to do the grunt job of merging stuff. Regards Antoine. _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
