This is a proposal to migrate Jira issues over to GitHub. See issue CB-13157
Currently, issues for all Cordova repos are tracked on Jira.
This proposal recommends that issues are mirgated from Jira to Github so that the issues are with the code. This is recommended because:
There are two potential options when using Github to track issues:
When issues are migrated to Github, each repository will contain its own set of issues. In each repo, there will be a list of the issues, which can be found under the Github “Issues” tab. Therefore, the issues can be found with the code. This can allow developers to reference pull requests more easily. Developers will also be able to “watch” repos and receive notifications when pull requests are sent or when new issues are created. We encourage and want to make it easy for committers to watch Github for the repos they want to be involved in.
When issues are migrated to Github, they are added to one “issues” repository. There will be one master “issues” repo that can track all of the Cordova issues on GitHub.
In both of these scenarios, issues are migrated over from Jira to Github. Jira will continue to be around for security issues. Alternatively, we could use a private GitHub repo for security tracking (if private repos are an option on the Github Apache org).
There will also be standard labels to follow to help tag each issues. It would be nice to agree on a suggested labels list to help tag and organize issues. List of potential labels include:
Update documentation: