Re: [DISCUSS] Moving JIRA issues to Github

Filed: https://issues.apache.org/jira/browse/INFRA-14901 On Thu, Aug 17, 2017 at 3:28 PM, Shazron wrote: > I'm afraid that will be something INFRA would need to do. As part of the > Gitbox project, the repo is moved from git-wip-us.a.o to gitbox.a.o > > So for example, this

Re: [DISCUSS] Moving JIRA issues to Github

I'm afraid that will be something INFRA would need to do. As part of the Gitbox project, the repo is moved from git-wip-us.a.o to gitbox.a.o So for example, this issue: https://issues.apache.org/jira/browse/CB-4725 Has the old link:

Re: [DISCUSS] Moving JIRA issues to Github

Thanks, Shazron. I think that clears up all my questions on issues. I have a question about the code move though. I was looking into an older Jira item today and noticed that all the links to cordova-android commits fail. Is it possible to make the original repositories mirrors of the Github ones

Re: [DISCUSS] Moving JIRA issues to Github

Clearing up some questions here. @dpogue --- True, we will have to rely on users filing issues in the right place. JIRA however, does not make it easy to do that since they start with a blank slate. When a user files an issue on a repo, they 95% know it applies to that repo. The 5% of the time

Re: [DISCUSS] Moving JIRA issues to Github

Also, we are trying to formalize the proposal at https://github.com/cordova/cordova-discuss/pull/75 On Wed, Aug 9, 2017 at 10:20 AM, Steven Gill wrote: > For security, we already get requests sent to our private mailing list ( > priv...@cordova.apache.org). We then

Re: [DISCUSS] Moving JIRA issues to Github

For security, we already get requests sent to our private mailing list ( priv...@cordova.apache.org). We then create a private issue to track the problem and only make it public once we solve the problem and do a release. Instead of a private jira instance, we could use a private github repo.

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,

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

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

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

>> 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

> The one I was thinking of was cordova-plugins. Do we want some way to track > issues for inactive platforms too or should those be considered permanently > closed? Possibly. I think we will still have JIRA around w/ deprecated components, maybe? I'm not sure. Shaz? > For example a new platform

Re: [DISCUSS] Moving JIRA issues to Github

>> Since it looks like not all repositories will be migrated where should their issues go? > All repositories will be migrated. The one I was thinking of was cordova-plugins. Do we want some way to track issues for inactive platforms too or should those be considered permanently closed? >> What

Re: [DISCUSS] Moving JIRA issues to Github

> Since it looks like not all repositories will be migrated where should their > issues go? All repositories will be migrated. > What about issues for repositories that don’t yet exist Can you give me an example? > or cross-cutting issues? I think if you absolutely need issues related to

Re: [DISCUSS] Moving JIRA issues to Github

I have a few questions about moving issues to GitHub. I haven’t used Github issues much so these all may be easily solvable. * Since it looks like not all repositories will be migrated where should their issues go? What about issues for repositories that don’t yet exist or cross-cutting issues? *

Re: [DISCUSS] Moving JIRA issues to Github

If people post their issue at the wrong repo (which of course can and will happen from time to time), there is a way to move them over with minimal loss of information: https://github.com/ionic-team/ionic/issues/12542 https://github.com/ionic-team/ionic-cli/issues/2597 This works for issues

Re: [DISCUSS] Moving JIRA issues to Github

I think the ease of use of GitHub issues overcomes potential problems about cross-referencing issues. Worth noting on this topic that GitHub already provides good support for referencing pull requests from issues across repos / orgs. The benefit of having issues and PRs in one place, to me, is a

Re: [DISCUSS] Moving JIRA issues to Github

My concern with GitHub issues is that we have a tonne of repos and issues can easily span across them, and we'd lose the one central place for issue tracking and triage. I worry that we'd be inundated with issues on the wrong repos, or without additional information, and triaging would become an

[DISCUSS] Moving JIRA issues to Github

Phase 1 of our move to Github is complete, see: https://issues.apache.org/jira/browse/INFRA-14347 We need a migration plan for moving JIRA issues to Github Issues before we enable Github Issues on those repos. Once we figure those out, we can proceed with Phase 2: