I agree this is a mess. I think we have previously taken the view that JIRA should be the permanent record of discussion, and that as such the git conversation should be duplicated there.
However, I think it would be better for JIRA to get a summary of important discussions, by one of the participants, not an illegible duplication of a page of code diffs attached to every one line nit comment. > On 30 Jul 2018, at 09:27, Stefan Podkowinski <s...@apache.org> wrote: > > Looks like we had some active PRs recently to discuss code changes in > detail on GitHub, which I think is something we agreed is perfectly > fine, in addition to the usual Jira ticket. > > What bugs me a bit is that for some reasons any comments on the PR would > be posted to the Jira ticket as well. I'm not sure what would be the > exact reason for this, I guess it's because the PR is linked in the > ticket? I find this a bit annoying while subscribed to commits@, > especially since we created pr@ for these kind of messages. Also I don't > really see any value in mirroring all github comments to the ticket. > #14556 is a good example how you could end up with tons of unformatted > code in the ticket that will also mess up search in jira. Does anyone > think this is really useful, or can we stop linking the PR in the future > (at least for highly active PRs)? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
