[Twisted-Python] [INFRASTRUCTURE OUTAGE] Moving from SVN to Git

Hi everyone! It's finally time to pull the trigger on this. Twisted's Trac may be down intermittently in the next few hours as I do the migration. - Amber

Hi everyone! Twisted infra is now back up and kicking, and we've moved to https://github.com/twisted/twisted as our "authoritative" mirror. - Amber

Hello Amber,
we've moved to https://github.com/twisted/twisted as our "authoritative" mirror.
are there any consequences of this for Twisted users and/or casual contributors? I used github source for a while not knowing it was not "authortiative" mirror, it always seemed fresh and updated. I remember some discussion on mailing list about moving issue tracking to github, is today's migration part of this process? Are there plans to accept pull requests on github? Paweł Miech 2016-05-10 18:29 GMT+02:00 Amber "Hawkie" Brown <hawkowl@atleastfornow.net>:

On Tue, 10 May 2016 at 20:38 Paweł Miech <pawelmhm@gmail.com> wrote:
The git mirror has been updated from the Subversion repository on commit for quite a while, so it was up to date, it just wasn't the correct place for committers to push changes to; this is what has changed now. I just got done editing a bunch of the wiki pages about the development process, primarily https://twistedmatrix.com/trac/wiki/TwistedDevelopment — so hopefully it should be clearer how to proceed now.
The main remaining problem with pull requests is that a committer has to push a branch to the main repository in order to run builds on the buildbots; this is due to issues around executing arbitrary code on the buildbots. Thus a PR-based workflow for non-committers currently doesn't make much sense. Issue tracking remains on Trac, at least for the forseeable future (implementing our workflow with GitHub issues is quite challenging).

Hi everyone! Twisted infra is now back up and kicking, and we've moved to https://github.com/twisted/twisted as our "authoritative" mirror. - Amber

Hello Amber,
we've moved to https://github.com/twisted/twisted as our "authoritative" mirror.
are there any consequences of this for Twisted users and/or casual contributors? I used github source for a while not knowing it was not "authortiative" mirror, it always seemed fresh and updated. I remember some discussion on mailing list about moving issue tracking to github, is today's migration part of this process? Are there plans to accept pull requests on github? Paweł Miech 2016-05-10 18:29 GMT+02:00 Amber "Hawkie" Brown <hawkowl@atleastfornow.net>:

On Tue, 10 May 2016 at 20:38 Paweł Miech <pawelmhm@gmail.com> wrote:
The git mirror has been updated from the Subversion repository on commit for quite a while, so it was up to date, it just wasn't the correct place for committers to push changes to; this is what has changed now. I just got done editing a bunch of the wiki pages about the development process, primarily https://twistedmatrix.com/trac/wiki/TwistedDevelopment — so hopefully it should be clearer how to proceed now.
The main remaining problem with pull requests is that a committer has to push a branch to the main repository in order to run builds on the buildbots; this is due to issues around executing arbitrary code on the buildbots. Thus a PR-based workflow for non-committers currently doesn't make much sense. Issue tracking remains on Trac, at least for the forseeable future (implementing our workflow with GitHub issues is quite challenging).
participants (3)
-
Amber "Hawkie" Brown
-
Paweł Miech
-
Tristan Seligmann