<Progress report and announcement>

Issue migration has been started. Jira is now read-only.

GitHub issue is available for new issues.

- You should open new issues on GitHub. E.g.
https://github.com/apache/lucene/issues/1078
- Do not touch issues that are in the middle of migration, please. E.g.
https://github.com/apache/lucene/issues/1072
  - While you cannot break these issues, migration scripts can
modify/overwrite your comments on the issues.
- Pull requests are not affected. You can open/update PRs as usual. Please
let me know if you have any trouble with PRs.


Tomoko


2022年8月18日(木) 18:23 Tomoko Uchida <tomoko.uchida.1...@gmail.com>:

> Hello all,
>
> The Lucene project decided to move our issue tracking system from Jira to
> GitHub and migrate all Jira issues to GitHub.
>
> We start issue migration on Monday, August 22 at 8:00 UTC.
> 1) We make Jira read-only before migration. You cannot update existing
> issues until the migration is completed.
> 2) You can use GitHub for opening NEW issues or pull requests during
> migration.
>
> Note that issues should be raised in Jira at this moment, although GitHub
> issue is already enabled in the Lucene repository.
> Please do not raise issues in GitHub until we let you know that GitHub
> issue is officially available. We immediately close any issues on GitHub
> until then.
>
> Here are the detailed plan/migration steps.
> https://github.com/apache/lucene-jira-archive/issues/7
>
> Tomoko
>

Reply via email to