And already activated:
https://github.com/apache/cordova-windows/issues
2018-02-19 17:04 GMT+01:00 Jan Piotrowski :
> Issue created: https://issues.apache.org/jira/browse/INFRA-16061
>
> 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
Issue created: https://issues.apache.org/jira/browse/INFRA-16061
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 fo
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 handl
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-t
+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.
> https://issues.apache.org/jira/browse/INFRA
>
> On Tue, Feb 13, 2018 at 10:58 PM, Jan Piotrowski
> 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
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
>