Am 19.02.2014 01:05, schrieb Larry Hastings: > On 02/18/2014 03:56 PM, Matthias Klose wrote: >> Am 19.02.2014 00:46, schrieb Larry Hastings: >>> On 02/18/2014 03:38 PM, Matthias Klose wrote: >>>> Am 17.02.2014 00:25, schrieb Larry Hastings: >>>>> And my local branch will remain private until 3.4.0 final ships! >>>> sorry, but this is so wrong. Is there *any* reason why to keep this branch >>>> private? >>> Yes. It ensures that nobody can check something into it against my wishes. >>> Also, in the event that I cherry-pick revisions out-of-order, it allows me >>> to >>> rebase, making merging easier. >>> >>> Is there *any* reason to make this branch public before 3.4.0 final? >> - Python is an open source project. Why do we need to hide >> development for a month or more? >> >> - Not even four eyes looking at the code seems to be odd. You >> can make mistakes too. >> >> This seems to be a social or a technical problem. I assume making this >> branch >> available read-only would address your concerns? Does hg allow this? And if >> not, why not create this branch in the upstream repository, and tell people >> not >> to commit to it? Why shouldn't such a social restriction work? Seems to >> work >> well for other projects. > > When you are release manager for Python, you may institute this policy if you > like. Right now, I have enough to do as it is.
is it too much to ask for a public mirror / tarball / something of this branch? This seems to be a minor effort compared to the clinic work that went into 3.4. Matthias _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
