can we have an up to date list of initial test migrations before talking about 
large scale?

I see 2 tracking lists:

1. 
https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching
   with 8 GH Issues enabled for 4 Jira projects: MPOM, MASFRES, ARCHETYPE, 
MNGSITE
   2 "copied issues" to be discussed

2.https://github.com/support-and-care/jira-to-gh-issues/blob/master/docs/migration-status-report.adoc
   adds MCLEAN, MJLINK, MSITE, MVERIFIER as WIP
   but does not list MPOM nor ARCHETYPE as WIP

this gives us 8 Jira migration WIP: that's quite a lot for a first step
I'm a little bit worried about going too fast at too large scale, without 
really understanding what options in terms of "migration" are available and done

on "copied issues" vs other way to talk about "migration":
- MNGSITE seems to be defined as "done", IIUC, but Wiki says "no copied issues" 
while S&C sqys "Only migrate open issues"
what's reality?
- MASFRES is "no copied issues" and S&C says wrongly that there is no issues 
history to migrate

this could be a good test for defining/testing capabilities for history 
migration, isn't it?


what's the focus and status, please?

and please, don't start MNG for now, as it's one of the most critical and 
complex beast
I see many approvals https://github.com/apache/maven/pull/1925 that make me 
fear a lot

Regards,

Hervé

Le lundi 6 janvier 2025, 09:20:39 CET Slawomir Jaranowski 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





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to