> On Oct 7, 2016, at 2:18 PM, Christopher Jones <jon...@hep.phy.cam.ac.uk> > wrote: > > >> On 7 Oct 2016, at 8:12 pm, Ryan Schmidt <ryandes...@macports.org> wrote: >> >> >>> On Oct 7, 2016, at 1:40 PM, Lawrence Velázquez <lar...@macports.org> wrote: >>> >>>> On Oct 7, 2016, at 2:09 PM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: >>>> >>>> Currently, once they find out about svn, and trac >>> >>> We will still use Trac for issue tracking, although I believe someone is >>> looking into integrating GitHub sign in. >> >> Rainer and Clemens looked into this and got it up and running on our test >> installation. >> > > So what exactly does this mean ?
It means you will log in to our Trac installation using your GitHub credentials, instead of via Mac OS Forge credentials as it is now. > Because, honestly, once the migration to GitHub is done unless comments sent > to a github pull request are automatically sync’ed to trac, and vice versa, I > do not see how trac can be maintained as a via system for discussing the pull > requests (and frankly I din’t really see why you would want to). There will be no syncing of anything between GitHub pull requests and Trac tickets because they are different entities. Trac tickets are where bug reports and other issues will be filed. Currently, if someone has a fix for an issue, they would attach a patch to the Trac ticket; in future, they will instead open a GitHub pull request and paste a link to the pull request into the ticket (or paste a link to the Trac ticket into the pull request; I'm not sure if we've decided that detail yet). And as Rainer said, there may be some simple changes for which it is sufficient to just submit a pull request, without opening a corresponding Trac ticket. We haven't defined what those situations would be yet. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
