Hi Jim, Not sure what you mean exactly. Of course there's a difference between git and GitHub... but we're talking specifically about GitHub integration. See the article linked on the original post: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
I'm +1 for the integration too. alex On Fri, Feb 14, 2014 at 6:34 AM, Jim Jagielski <j...@jagunet.com> wrote: > git != Gitub. ie: moving to git is not the same as > using Github. > On Feb 13, 2014, at 12:34 PM, Antoine Toulme <anto...@lunar-ocean.com> > wrote: > > > I would be delighted if we move to git and open ourselves to a wider > > audience of developers. You have my vote of course. > > > > > > On Wed, Feb 12, 2014 at 1:25 PM, Peter Donald <pe...@realityforge.org > >wrote: > > > >> Hi, > >> > >> The infrastructure team just announced [1] that they now support > >> improved integration with GitHub. In a nutshell this means > >> > >> " > >> * Any Pull Request that gets opened, closed, reopened or commented on > >> now gets recorded on the project's mailing list > >> * If a project has a JIRA instance, any PRs or comments on PRs that > >> include a JIRA ticket ID will trigger an update on that specific > >> ticket > >> * Replying to a GitHub comment on the dev@ mailing list will trigger a > >> comment being placed on GitHub (yes, it works both ways!) > >> " > >> > >> If there is no objections I would like to see it turned on for Buildr. > >> > >> [1] > >> > https://blogs.apache.org/infra/entry/improved_integration_between_apache_and > >> > >> -- > >> Cheers, > >> > >> Peter Donald > >> > >
