[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-10557:
-----------------------------------
Description:
A few (not the majority) Apache projects already use the GitHub issue instead
of Jira. For example,
Airflow: [https://github.com/apache/airflow/issues]
BookKeeper: [https://github.com/apache/bookkeeper/issues]
So I think it'd be technically possible that we move to GitHub issue. I have
little knowledge of how to proceed with it, I'd like to discuss whether we
should migrate to it, and if so, how to smoothly handle the migration.
The major tasks would be:
* (/) Get a consensus about the migration among committers
* (/) Choose issues that should be moved to GitHub
** Discussion thread
[https://lists.apache.org/thread/1p3p90k5c0d4othd2ct7nj14bkrxkr12]
** Conclusion for now: We don't migrate any issues. Only new issues should be
opened on GitHub.
* Build the convention for issue label/milestone management
** Do some experiments on a sandbox repository
[https://github.com/mocobeta/sandbox-lucene-10557]
** Make documentation for metadata (label/milestone) management
* Enable Github issue on the lucene's repository
** Raise an issue on INFRA
** (Create an issue-only private repository for sensitive issues if it's
needed and allowed)
** Set a mail hook to issues@lucene.apache.org
* Set a schedule for migration
** Give some time to committers to play around with issues/labels/milestones
before the actual migration
** Make an announcement on the mail lists
** Show some text messages when opening a new Jira issue (in issue template?)
was:
A few (not the majority) Apache projects already use the GitHub issue instead
of Jira. For example,
Airflow: [https://github.com/apache/airflow/issues]
BookKeeper: [https://github.com/apache/bookkeeper/issues]
So I think it'd be technically possible that we move to GitHub issue. I have
little knowledge of how to proceed with it, I'd like to discuss whether we
should migrate to it, and if so, how to smoothly handle the migration.
The major tasks would be:
* Get a consensus about the migration among committers
* Enable Github issue on the lucene's repository (currently, it is disabled on
it)
* Build the convention or rules for issue label/milestone management
* Choose issues that should be moved to GitHub (I think too old or obsolete
issues can remain Jira.)
> Migrate to GitHub issue from Jira
> ---------------------------------
>
> Key: LUCENE-10557
> URL: https://issues.apache.org/jira/browse/LUCENE-10557
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Tomoko Uchida
> Assignee: Tomoko Uchida
> Priority: Major
>
> A few (not the majority) Apache projects already use the GitHub issue instead
> of Jira. For example,
> Airflow: [https://github.com/apache/airflow/issues]
> BookKeeper: [https://github.com/apache/bookkeeper/issues]
> So I think it'd be technically possible that we move to GitHub issue. I have
> little knowledge of how to proceed with it, I'd like to discuss whether we
> should migrate to it, and if so, how to smoothly handle the migration.
> The major tasks would be:
> * (/) Get a consensus about the migration among committers
> * (/) Choose issues that should be moved to GitHub
> ** Discussion thread
> [https://lists.apache.org/thread/1p3p90k5c0d4othd2ct7nj14bkrxkr12]
> ** Conclusion for now: We don't migrate any issues. Only new issues should
> be opened on GitHub.
> * Build the convention for issue label/milestone management
> ** Do some experiments on a sandbox repository
> [https://github.com/mocobeta/sandbox-lucene-10557]
> ** Make documentation for metadata (label/milestone) management
> * Enable Github issue on the lucene's repository
> ** Raise an issue on INFRA
> ** (Create an issue-only private repository for sensitive issues if it's
> needed and allowed)
> ** Set a mail hook to issues@lucene.apache.org
> * Set a schedule for migration
> ** Give some time to committers to play around with issues/labels/milestones
> before the actual migration
> ** Make an announcement on the mail lists
> ** Show some text messages when opening a new Jira issue (in issue template?)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
