Enable GitHub issues

[gnodet]

No description provided.

[kwin]

I think this deserves some official vote on the mailing list and a JIRA issue outlining details:
Release Notes
Parallel usage of JIRA or migration?

[olamy]

can we have this one read only first https://issues.apache.org/jira/projects/MNG/
and with some messages to redirect to correct location to create issues now.

[cstamas]

The discussion, just FTR
https://lists.apache.org/thread/v23tj8s8f6oyrmbyn1m6xg2pv7k92n4p

[gnodet]

@olamy
Imho it's a bit premature to just make the jira project read only. We can definitely add some warning and maybe disallow the creation of new issues (if possible). But we still have issues there and I certainly don't want to duplicate issues. I know Apache SSHD has gone through the same kind of migration some time ago. New issues were created on GH, but existing ones have not been migrated. We ended identifying with [GH-xxx] for the GitHub ones and [SSHD-xxx] for the JIRA issues. For some time, the release notes contained both kind of issues, but over time, the migration is done painlessly imho.

[olamy]

My only concern is to have new issues created in Jira.
Is there any way to at least prevent creating new issue in Jira?

[gnodet]

My only concern is to have new issues created in Jira.

Yes, agreed.

Is there any way to at least prevent creating new issue in Jira?

I think it should be doable from
https://issues.apache.org/jira/plugins/servlet/project-config/MNG/permissions
We need to investigate further and the profile seems shared between all maven projects for now.
Or maybe we switch all repos to GH issues at the same time.

[olamy]

My only concern is to have new issues created in Jira.

Yes, agreed.

Is there any way to at least prevent creating new issue in Jira?

I think it should be doable from https://issues.apache.org/jira/plugins/servlet/project-config/MNG/permissions We need to investigate further and the profile seems shared between all maven projects for now. Or maybe we switch all repos to GH issues at the same time.

Yes. all at the same time looks good to me.

maybe we can have some tools to copy one specific jira issue to GH? (when working on it)

[CrazyHZM]

Enabling the GitHub issue gives Maven more user feedback, so it looks good.

[slachiewicz]

We should also be prepared to move issues reported here to the correct place like plugins, shared lib

[slawekjaranowski]

We should also be prepared to move issues reported here to the correct place like plugins, shared lib

We can move issues between github projects - there is an option transfer issue ....

[slawekjaranowski]

I'm for enabled issues here and disable possibility to creating new issues in JIra

[slawekjaranowski]

We also should first finish - apache/maven-site#588 to have some guide how to works with GitHub issues in all our project in the same way.