First we need to enable issues on GitHub to allow migrating issues. So please add a column "GitHub Issues enabled"
Thanks for the feedback. I added another column.
I'm still not sure if we need to copy issues for all projects - up to you.
My preferred way is to migrate all issues for all projects. Maybe I'm too optimistic, but with the automation, it should not be so big effort.
IMHO in the long term, it will be easier to search for elder issues.
Sandra I assume that you will update such a list as in a repository where Maven committers can not update it.
Yes, it is not the best location. I didn't know it better. Do you know a better place? Maybe a separate repository?
By the way, thanks for your effort.
You are welcome :) Am 06.01.25 um 13:47 schrieb Slawomir Jaranowski:
On Mon, 6 Jan 2025 at 13:15, Sandra Parsick <spars...@web.de.invalid> wrote:Hi, I created an overview about the Jira Project that are Maven related (I used the project category 'Maven' and ignored retired projects) [1]. I will start creating migration configuration based on that list. Do you have prefered order? Did I miss any projects?First we need to enable issues on GitHub to allow migrating issues. So please add a column "GitHub Issues enabled" I'm still not sure if we need to copy issues for all projects - up to you. As I know we need copy issues to help users search to avoid creating duplicates. I would like to observe if such problems will occur in simple, not often changed repositories. Sandra I assume that you will update such a list as in a repository where Maven committers can not update it. By the way, thanks for your effort.- Sandra [1] https://github.com/support-and-care/maven-support-and-care/issues/79 Am 06.01.25 um 09:34 schrieb Slawomir Jaranowski:On Mon, 6 Jan 2025 at 09:26, Guillaume Nodet <gno...@apache.org> wrote:Is there any way to make the JIRA for migrated projects read-only, or at least disable the creation of new issues ? That would help a lot in guiding existing contributors to GitHub for new issues.There is a ticket for infra ... https://issues.apache.org/jira/browse/INFRA-26406 I created it after enabling issues ...Le lun. 6 janv. 2025 à 09:21, Slawomir Jaranowski <s.jaranow...@gmail.com> a écrit :Hi, Last time I enabled GitHub issues in https://github.com/apache/maven-site I don't have a plan to copy old issues for this project from jira to GitHub. Now I'm working on next repo - https://github.com/apache/maven-apache-resources/pull/23 In next I will use the similar issues templates We have about 100 repositories to do the same work, I don't know how many people want to be informed about it .... and for others it can be spam ... The questions - how we should work on such tasks ... 1. should we informa on dev ML - about starting working on the next repository? 2. should we send a mail to dev (and maybe also users) ML after switching? 3. maybe PR will be enough to discuss work on specific repository for such technical task -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org-- ------------------------ Guillaume Nodet --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
OpenPGP_signature.asc
Description: OpenPGP digital signature
