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]).


2018-02-13 16:52 GMT+01:00 Shazron <shaz...@gmail.com>:
> 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:
> +1.
> You need to file an issue with INFRA.
> https://issues.apache.org/jira/browse/INFRA
> On Tue, Feb 13, 2018 at 10:58 PM, Jan Piotrowski <piotrow...@gmail.com>
> 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: https://issues.apache.org/jira/issues/?jql=project%20%
> 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: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org

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

Reply via email to