[INFO] Phase 1 of JIRA to GitHub issues migration completed

Matthias Bünger <[email protected]>
Newsgroups gmane.comp.jakarta.turbine.maven.user
Message-ID <[email protected]>
Greetings everyone,
I want to give you all a status information about our progress to 
migrate issues from JIRA to Github issues.

As a reminder and for those who are not aware:
Last december we decided to migrate to Github Issues. Three of the 
reasons for this were

* issues and source code are closer to each other
* a better markdown support and
* a better accessibility for users, because a lot of people already own 
a GitHub account (to create issues in ASF-JIRA you need to apply for an 
account first)

See discussion thread [1] for more details.


The whole "project" is divided into two phases:

1) The goal of this first phase was to enable Github issues for all 
active Maven projects/components, including disabling the creation of 
new issues in the JIRA.
2) The second phase is the acutal migration of existing JIRA issues to 
GitHub.

For phase 1 I write "was", because with Maven 3.9.10 released today, I 
just enabled Github Issues for the Maven Core Github repository, which 
was the last repository left to enable GitHub issues. During the next 
days issue the creation in the according JIRA project (and two others) 
will get disabled by INFRA. Updating of existing issues will still be 
possible!
I want to thank Slawek Jaranoswki here, for his hard work on reviewing 
far more than 100 of almost identical PR, which only differ in minor 
things individual to the according repository/project - thank you! :drink:

The second phase runs in parallel to phase 1. Benjamin Marwell and 
Sandra Parsick have prepared and tested the migration tool and already 
migrated issues of some, mostly smaller, JIRA projects after GitHub 
issues were enabled for those. Thank you very much! :party:
I'm happy to join them now, so we can continue migrating issues together.

One note about phase 2: We can (and do) only disabled notification to 
the issues mailing list for the time of actual migration, but we can't 
disable them for the whole repository. This means that if you watch a 
GitHub repository where issues will be migrated to, you might get a 
large amount of mails about this!


That's all I can think of. Enjoy the weekend, writing issues on GitHub 
and of course todays releases of Maven 3.9.10!

Greetings
Matthias


[1]: https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.