Just ask INFRA to enable GH issues on the repo, point them to the repo you
want (in this case cordova-windows only), simple as that. As long as we
have consensus of course, and I don't believe anyone will object.

Issues on JIRA need to be either resolved, or migrated to GH (this will be
some non-trivial work, which would need to be done anyway if we move other
components to GH).

A resolution could be closing the issue, and telling the issue reporter to
file it on GH now if it is still relevant. But any new issues for the
component should be closed, with the pointer to the new location.

On Feb 13, 2018 at 11:43 PM, Chris Brody <chris.br...@gmail.com> wrote:

+1 (+100) on my part

@Shazron what should we expect INFRA to do to help us with this one?

On Tue, Feb 13, 2018 at 10:29 AM, Shazron <shaz...@gmail.com> wrote:

You need to file an issue with INFRA.

On Tue, Feb 13, 2018 at 10:58 PM, Jan Piotrowski <piotrow...@gmail.com>

Hi all!

As I am working towards a (bumpy...) 6.0.0 release of cordova-windows,
I also went through its JIRA issues again and resolved, closed or
moved some of them. I noticed that we are down to 1 page of ~50
issues: https://issues.apache.org/jira/issues/?jql=project%20%
Many of those are actually for plugins that have problems with the
Windows platform, only a hand full are actual current problems (and
most of those I hope to have resolved before the release).

Because of that I think `cordova-windows` would be an excellent
candidate to be the first Cordova repo in the apache org to activate
GitHub issues! No need to migrate anything and in the release blog
post for cordova-windows 6.0.0 we could already link to the GitHub
issues page for bug reports and feedback.

What do you think?
What has to happen to make this a reality?


To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to