This is brought up roughly once per year. If anything, you're a bit behind schedule
https://lists.apache.org/thread.html/0750a01682eb36374e490385d6776669ac86ebc02efa27a87b2dbf9f%40%3Cdev.cassandra.apache.org%3E https://lists.apache.org/thread.html/c21ccedc7fbda18558997dee8f86c074514b67387858ec1268c47685%40%3Cdev.cassandra.apache.org%3E https://lists.apache.org/thread.html/d327a48b6644aecba8d48f31afcba4dff65d97946db2d622186c004f%40%3Cdev.cassandra.apache.org%3E On 22/01/2020, 22:21, "David Capwell" <dcapw...@gmail.com> wrote: When submitting or reviewing a change in JIRA I notice that we have three main patterns for doing this: link branch, link diff, and link GitHub pull request (PR); I wanted to bring up the idea of switching over to GitHub pull requests as the norm. Why should we do this? The main reasons I can think of are: consistency within the project, common pattern outside and inside Apache (not a new process for new members to learn), PRs are easier to review and comment on (much easier than linking lines in a branch), Github and JIRA integration is already present so all conversations will be added to the JIRA work log, and could be linked with Jenkins to trigger builds and tests and to report the status into JIRA. How would one start to do this? 1. Include the JIRA link in a commit message (example: CASSANDRA-<number> : message) 2. Create pull request (when creating the branch, the git message provides a link to create a pull request) That is it, by doing those two steps JIRA will be updated with all Github conversations, Jenkins could be notified and start building and report back to JIRA. Thoughts? References: - https://www.apache.org/dev/svngit2jira.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
