I always thought (and think so even now) that having JIRA ticket associated with a PR helps in better tracking of the changes that go in. JIRA ticket is kind of go-to place to know about the change, type of change, the issue that is being resolved, links to the documentation, forum discussion etc…
Is the plan to make PR as the place to get all that information and scrap JIRA in the long run?
The proposal is not to go scrap Jira. We will have open jira and that will remain the OSS bug tracking system. However, like other open source projects, we would not be required to mandatorily have a jira-id before some code can be contributed. If you look at most open source github repos, this is the way they work. The pull requests completely describe what is being done. Contributors would be free to add more information into (new/existing) jira ticket(s) if they want.
To give you an example of how few other open source projects looks like do have a look at these large projects:
I like this proposal – it should simplify a lot of cases without losing any information.
In particular, if someone has a fix for a bug, they can simply submit the pull request with all the info – there’s no need to duplicate the info in a JIRA ticket. (JIRA is still useful when someone finds a bug … and doesn’t have a fix… yet.)
I think migrating from JIRA to GitHub issue won’t be a much problem as both has API which we can make use of to migrate using some sort of script…
When I search on internet and I find this https://github.com/hbrands/jira-issues-importer
I like the overall proposal. Just want a clarification, it doesn’t matter which issue tracker we choose, github or JIRA, it would still not be mandatory for contributing code correct? (except for the cases where there is a bug but no fix )
BTW, I like the github issue tracker over jira (aside from this proposal). The challenges i can think of are:
Migrating existing bugs.
Updating the merged PR’s which had references to Jira tickets: Do we go and update those references to the github issue tracker references. Or, we make the existing jira issue tracker read-only so the references are intact (for the old PRs), but any new activity happens in github issue-tracker (this could be confusing to users anyway)…
I agree that it would be confusing, especially if we create a Github Issues copy of it, so maybe this is another thing that needs to be taken care of while migrating, and if that’s not easy to do, then maybe it’s not worth it.
Exactly @minghui. I was suggesting the same. We can use github issues from clean state. That would mean that we continue to keep our current Jira repo around, perhaps in read-only mode (just as a reference for older PR’s that reference Jira).
Matching the topic of discussion with the topic subject helps ensure good visibility among the community, and it allows people to use the per-topic notification features of the forum without worrying about missing important discussions.