[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543572#comment-17543572
]
Tomoko Uchida edited comment on LUCENE-10557 at 5/29/22 6:44 AM:
-----------------------------------------------------------------
Migration plan (an early draft)
* Set a criteria which issues should be migrated to GitHub issue
** e.g. Migrate all unresolved issues
* Set an operational policy for version/metadata management
** Kubernetas's and Apache Airflow's method looks good to me
** Map current JIRA metadata to GitHub milestones/labels
** ... needs some trials and errors with a sandbox repository
* Prepare migration scripts
* Enable GitHub issue (raise an issue on INFRA)
* Set a schedule for migration
was (Author: tomoko uchida):
Migration plan (an early draft)
* Set a criteria which issues should be migrated to GitHub issue
** e.g. Migrate all unresolved issues
* Set an operational policy for version/metadata management
** Kubernetas's and Apache Airflow's method looks good to me
** Map current JIRA metadata to GitHub milestones/labels
** ... needs some trials and errors with a sandbox repository
* Prepare migration script
* Enable GitHub issue (raise an issue on INFRA)
* Set a schedule for migration
> 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
> 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
> * 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.)
--
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
