Re: [DISCUSS] Moving JIRA issues to Github

>> As a user, I’ll occasionally skim the recently opened bugs in Jira across >> the entire project to see if any may affect us. Is there going to be a way >> to do this with Github? Subscribing to notifications could be a work-around >> but it’s not ideal. > > Good question. I can't really

Re: [DISCUSS] Moving JIRA issues to Github

What about security issues? El 3 ago. 2017 4:53 a. m., "Jan Piotrowski" escribió: > >> As a user, I’ll occasionally skim the recently opened bugs in Jira > across the entire project to see if any may affect us. Is there going to be > a way to do this with Github?

Re: [DISCUSS] Moving JIRA issues to Github

I think the web interface is a good idea. It might help triage as well if you're able to search and filter issues across the entire project. I think it might need to have some mechanism for excluding or grouping migrated issues too. On Thu, Aug 3, 2017 at 5:55 AM, julio cesar sanchez

[GitHub] cordova-plugin-geolocation pull request #92: CB-12895 : Added eslint and rem...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-geolocation/pull/92 CB-12895 : Added eslint and removed jshint ### Platforms affected ### What does this PR do? Added eslint and removed jshint ### What testing

Re: [DISCUSS] Moving JIRA issues to Github

Did a little searching, and GitHub has a global issue search you can use: https://github.com/issues Combine that with a custom search query, essentially a giant chain of (repo:apache/cordova-browser or repo:apache/cordova-android) etc., and I think you could get what you want. On Thu, Aug 3,

[GitHub] cordova-plugin-file pull request #214: CB-12895 : Setup eslint and removed j...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-file/pull/214 CB-12895 : Setup eslint and removed jshint ### Platforms affected ### What does this PR do? Setup eslint and removed jshint ### What testing has

[GitHub] dpogue commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit

dpogue commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit URL: https://github.com/apache/cordova-android/pull/389#issuecomment-320067936 So I ran this branch with the following: ``` cordova create androidTest cd ./androidTest cordova platform

[GitHub] macdonst commented on issue #399: CB-12730: Compat - INTEGRATE

macdonst commented on issue #399: CB-12730: Compat - INTEGRATE URL: https://github.com/apache/cordova-android/pull/399#issuecomment-320087845 @infil00p I was thinking testing for this would be handled at the plugin level as it is what is requesting the permissions. Hard to instrument these

[GitHub] infil00p commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit

infil00p commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit URL: https://github.com/apache/cordova-android/pull/389#issuecomment-320080278 @dpogue No, that's definitely a bug. Only the app directory should exist, and it's clear that something else is

[GitHub] filmaj commented on issue #399: CB-12730: Compat - INTEGRATE

filmaj commented on issue #399: CB-12730: Compat - INTEGRATE URL: https://github.com/apache/cordova-android/pull/399#issuecomment-320116296 Sounds like lazy consensus on the tests is "nah" This is an automated message from

[GitHub] filmaj commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit

filmaj commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit URL: https://github.com/apache/cordova-android/pull/389#issuecomment-320108011 https://github.com/infil00p/cordova-android/blob/StudioProjectCompat/bin/templates/cordova/lib/prepare.js#L214-L216

Re: [DISCUSS] Moving JIRA issues to Github

> What about security issues? > Right now on jira we have private security issues not visible for the regular > people and as far as I know, we can't do that on GitHub Initial idea: Have an email address where people can send messages to, the recipient then creates an issue on a private Github