Any news?
Even after reading around, I still don't know how JIRA fits in (if at
all). It might only send emails c.f commits@.
A github only flow is fine by me. Loosing JIRA will be a bump but it is
a question of balance - more GH input vs undoing what we have talked
about for some time (JIRA). or we have to run both nodes (not so different).
e.g.
http://opennlp.apache.org/using-git.html
Any other good links?
(there is more that we can do with the contribution process like ask for
one-commit (mostly) contributions,
Of course, all this takes time to do, like documentation.
The current GH-mirror workflow isn't that problematic at the moment
albeit it a few extra steps.
(the main annoyance for me is deleting local branch and the gitbox does
not change this one way of the other as far as I can see).
Andy
On 17/11/17 14:39, ajs6f wrote:
Hi, INFRA--
Here at Jena we are considering moving our Apache git <-> Github mirroring to
accept changes at Github and mirror them to Apache git (currently it's the other way
around). But right now we have some nice Jira integrations, and so we have some
questions about how that would work if we reversed the mirroring.
Currently, any mention of a Jira ticket (e.g. "I think this could affect
JENA-1234") in a Github PR automatically copies the conversation for that PR over to
the comments in that Jira ticket. Will we be able to keep that integration if we reverse
the mirroring?
Github treats issues/tickets and PRs very similarly-- is it possible to
integrate Jira in a similar way so that a PR that doesn't mention an extant
particular Jira ticket automatically files a new Jira ticket?
Thanks for any info and all that you already do for us!
ajs6f
