I suspect that my practices are out of step with Michael's practices
(and maybe other people's too). I prefer to work in JIRA as much as
possible, using git's review mechanism only for critiques of
individual lines. I do this because I like being able to see how a
contribution evolved, and the reasoning behind it, long after that
contribution has been merged. Github is not very good at preserving
Mirroring is all very well, but will it double the volume of email traffic?
I'm feeling rather burned out because I committed over 50 of other
people's PRs last release.
On Tue, Dec 4, 2018 at 3:02 PM Francis Chuang <francischuang@xxxxxxxxxx>
Thanks for taking this on, Michael!
I think this is a good idea as having to go back and forth between a
Github PR and JIRA issue can sometimes be a massive context switch. I
think Github comments are current mirrored into the appropriate JIRA
issue, but the reverse does not currently work.
If possible, I think this would also be a good idea for the
calcite-avatica and calcite-avatica-go repositories as well.
On 5/12/2018 6:56 am, Michael Mior wrote:
This discussion came up a while back, but I think it would be really
helpful to have JIRA comments mirror to the association GitHub issue.
reviewing PRs, I start by looking for those with no comments
someone else has already had a look). Then I have to dig up the JIRA
and check if someone has reviewed there. If there are no objections,
file a ticket with INFRA.