Also a “+1” from my side, as long as the integration with current Apache Git works flawless ;o)
Best Regards, Michael > On 14 Dec 2015, at 17:54, V.A, Chandan <[email protected]> wrote: > > +1 from me. > Initially we also were able to update the JIRA ticket ID automatically upon > committing to apache repo. This was possible if we include JIRA ticket ID > like [OLINGO-XXX] in the commit message. But suddenly it stopped working. > Maybe we need to bring that feature as well back. > > Regards > Chandan > > -----Original Message----- > From: Ramesh Reddy [mailto:[email protected]] > Sent: Monday, December 14, 2015 7:57 PM > To: [email protected] > Subject: Re: [DISCUSS] GitHub setup for Olingo > > +1 anything that improves workflow with GitHub is good news. Ability to look > up commits based on JIRA is very valuable. And the emails will serve as code > review invitations, which is great. > > Ramesh.. > > ----- Original Message ----- >> On 14/12/2015 14:52, Amend, Christian wrote: >>> Hi, >>> >>> It seems that the integration between Apache and GitHub is far more >>> advanced than I realized. According to this blog entry[1] one only has to >>> open a ticket with Infrastructure to get this enabled. These are some of >>> the features that can be enabled: >>> 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!) >>> >>> As far as I understood you still can`t use it as a primary repository. >>> Instead all changes are made at the Apache repo and once they are >>> replicated to GitHub they trigger the closing of a pull request there >>> automatically. This also means that the fancy UI features of GitHub for >>> merging can`t be used (please correct me here if I am wrong) >>> >>> What do you think about this? I personally would like to have a better >>> integration with GitHub. This should enable people to easier contribute to >>> Olingo. >> >> +1 >> >>> @ Francesco: You said you are using this for Syncope. Which features have >>> you enabled there and does it mean much overhead to work with it? And most >>> importantly is it enough to open a ticket with infrastructure or are there >>> additional steps needed to make this work? >> >> At Syncope we have enabled everything available :-) >> >> No overhead, AFAICT, and the only fancy think you actually miss is the >> "Merge" button - which needs to be replaced by a commit with log "This >> closes #X". >> >> In my own experience, a ticket to Infra does the job usually; sometimes >> a quick visit on >> >> https://s.apache.org/infrachat >> >> and some kindness help as well :-) >> >> Regards. >> >>> [1] >>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and >> >> -- >> Francesco Chicchiriccò >> >> Tirasa - Open Source Excellence >> http://www.tirasa.net/ >> >> Involved at The Apache Software Foundation: >> member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer >> http://home.apache.org/~ilgrosso/ >> >> >>
smime.p7s
Description: S/MIME cryptographic signature
