We have just released an update to our cordova-node-xcode tool!
- cordova-node-xcode@2.0.0
You can view the release blog post at
https://cordova.apache.org/news/2019/01/17/xcode-release-2.0.0.html
There was already a discussion about this and about using Probot.
As said before and still, I am in favor of adding Probot.
Let's add it before it falls off the radar again.
Previous Thread:
https://lists.apache.org/thread.html/e2d9912052bc274f449e56fb2e4a1b518536c34a3146076d3a65c0d6@%3Cdev.cord
The vote has now closed. The results are:
Positive Binding Votes: 4
* Bryan Ellis
* Chris Brody
* Ken Naito
* Gandhi Rajan
Negative Binding Votes: 0
The vote has passed.
On Tue, Jan 15, 2019 at 2:32 PM Bryan Ellis wrote:
> Please review and vote on this Cordova Node Xcode 2.0.0 Release
> by r
Nightly build #973 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/973/consoleFull
-
Jenkins for Apache Cordova
-
I would favor using the Probot move app. Anyone else?
I would be happy to raise another INFRA issue, with a link to this thread,
if we get a couple more +1 votes on this idea.
On Wed, Jan 16, 2019 at 8:39 PM Shazron wrote:
> Not sure what they think about installing Probot:
> https://probot.git
Not sure what they think about installing Probot:
https://probot.github.io/apps/move/
Seems like a good compromise -- since we have write permissions for
the source and target repos.
On Wed, Jan 16, 2019 at 11:47 PM Chris Brody wrote:
>
> Thanks guys. I completely get it that it is not possible t
Thanks guys. I completely get it that it is not possible to get what we
want according to the existing combination of INFRA rules and GitHub
behavior.
I find this to be pretty bad for usability and am hopeful that we may be
able to work towards a better solution, somehow. That is why I raised the
They have answered that they can transfer the issues we tell them to, but I
think it's easier/faster to just create a new one than creating an infra
ticket so they move it.
El mié., 16 ene. 2019 a las 16:39, Chris Brody ()
escribió:
> I already saw that in the GitHub docs. I raised the INFRA issu
I already saw that in the GitHub docs. I raised the INFRA issue in hopes
that we can find a solution, somehow.
On Wed, Jan 16, 2019 at 10:33 AM Darryl Pogue wrote:
> From the GitHub docs:
> > To transfer an open issue to another repository, you must have admin
> permissions on the repository the
>From the GitHub docs:
> To transfer an open issue to another repository, you must have admin
> permissions on the repository the issue is in and the repository you're
> transferring the issue to.
I don't think there's anything INFRA can do to enable it, since repo
admin isn't something they'll
Here is an example where I had to apply a clumsy workaround:
https://github.com/apache/cordova/issues/68
I submitted the following INFRA ticket:
https://issues.apache.org/jira/browse/INFRA-17671
+1
Ran coho audit-license-headers
Ran coho check-license
On Tuesday, January 15, 2019, Bryan Ellis wrote:
> Please review and vote on this Cordova Node Xcode 2.0.0 Release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> DISCUSS thread:
> https://lists.apache.org/thr
12 matches
Mail list logo
