You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Tomoko Uchida (Jira)" <ji...@apache.org> on 2022/05/04 11:36:00 UTC
[jira] [Updated] (LUCENE-10557) Migrate to GitHub issue from Jira?
[ 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
* 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.)
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
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org