Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable GitHub issues #1925

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

gnodet
Copy link
Contributor

@gnodet gnodet commented Nov 19, 2024

No description provided.

@kwin
Copy link
Member

kwin commented Nov 19, 2024

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
Copy link
Member

olamy commented Nov 20, 2024

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.

Copy link
Member

@cstamas cstamas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gnodet
Copy link
Contributor Author

gnodet commented Nov 20, 2024

@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
Copy link
Member

olamy commented Nov 20, 2024

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
Copy link
Contributor Author

gnodet commented Nov 20, 2024

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
Copy link
Member

olamy commented Nov 21, 2024

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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants