And already activated:

2018-02-19 17:04 GMT+01:00 Jan Piotrowski <>:
> Issue created:
> 2018-02-13 17:01 GMT+01:00 Jan Piotrowski <>:
>> Ok, thanks.
>> Then let's wait a bit to see if we get any -1 on this - then I will go
>> ahead and create the INFRA issue.
>> As this is our first repo I suggest we do _nothing_ in JIRA for now
>> but just point to the GitHub issues in the release blog post.
>> If everything goes well, we can decide how to handle issue migration
>> etc. for the other repos (and how to handle the remaining
>> cordova-windows issues [in this case manually closing them with a link
>> and note to refile if still relevant would be doable, but I guess not
>> for all other platforms and plugins]).
>> J
>> 2018-02-13 16:52 GMT+01:00 Shazron <>:
>>> 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 <> 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 <> wrote:
>>> +1.
>>> You need to file an issue with INFRA.
>>> On Tue, Feb 13, 2018 at 10:58 PM, Jan Piotrowski <>
>>> wrote:
>>> 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:
>>> 3D%20CB%20AND%20status%20in%20(Open%2C%20%22In%20Progress%
>>> 22%2C%20Reopened)%20AND%20component%20%3D%20cordova-windows
>>> 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?
>>> Best,
>>> Jan
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to