On 2016-10-07 20:58, Christopher Jones wrote: > >> On 7 Oct 2016, at 7: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.
Trac will stay. Clemens and I already wrote new modules for the trac-github plugin [1] in order to allow both login with GitHub as main authentication provider, migrating old tickets from mail addresses to the GitHub accounts and all permissions in Trac will be based on team memberships on GitHub. The only downside is that references to tickets will have to become full URLs to Trac, because GitHub claims the #12345 syntax for their own issue tracker and pull requests. Commits which contain such an URL will automatically be linked from the corresponding ticket. > Personally I think we have to migrate away from trac as well. Pull > requests in GitHub will largely replace what happens in trac for > submission of patches and the discussion of them. If we stick with > trac for issues then for me it will be an utter mess. Pull requests can be used in addition to tickets. For simple port updates, there will be no need to open a ticket. We evaluated several options, including issue trackers provided by GitHub, GitLab, BitBucket, JIRA, and also others and finally came to the conclusion that Trac is still the best option at hand. Especially with hosting our own installation, we will finally be able to make more modifications and use custom plugins, that we never got deployed at Mac OS Forge (for example [2]). Rainer [1] https://github.com/trac-hacks/trac-github [2] https://trac.macports.org/ticket/40987 _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
