On Thu, 6 Feb 2025 at 09:56, Herve Boutemy <hbout...@apache.org> wrote: > > On 2025/02/06 08:25:44 Slawomir Jaranowski wrote: > > On Thu, 6 Feb 2025 at 08:56, Hervé Boutemy <herve.bout...@free.fr> wrote: > > > > > > can we work on scaling the Jira to GH Issues first before diving into all > > > the > > > > What do you think about "scaling the Jira to GH Issues"? > > where we are > https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching > job: > - quite done on 2 (without migration) + 3 where there are no Jira origin > - started on 11 > > target scale: ~ 80 = https://maven.apache.org/scm.html
So I think we should do it step by step, not all in once. For me there are two task: - some of cleanups and enable GitHub Issues - copy old issues from jira to GitHub Why should we stop with the first task .... it has value itself. > > > > > > implications of Maven 3 vs Maven 4 compatibility topic? > > > > > > I feel we launch too much large scale and critical topics in parallel > > > > Topics about the Maven 3 vs 4 version are resolved > > I don't see any critical issues ... > "issues", i don't know: you started to explicit que question of Git branches, > documentation, release drafter Git branches and documentation topic is an issue not connected with GitHub issues - for Jira we have the same question. release drafter - resolved and described: https://github.com/apache/maven-gh-actions-shared#release-drafter-configuration > but near 50 plugins = https://maven.apache.org/scm.html > even defining how we really expect to manage 2 branches with our resources > has to be clarified Not connected with GitHUb issues - the same is with Jira > > > > > Scale is not a large for me > please take time to look at figures and effective progress (and discussions > in parallel) and community members really ready to work on doing and > finishing the actual started work we always have a parallel work and task in progress .... I'm interested in who wants to works on GitHub issues but doesn't have time due to current tasks? Maybe someone else who doesn't have tasks in progress wants to join such work. > > in addition, we're currently hit by the privacy change > > > > > > > > > Regards, > > > > > > Hervé > > > > > > Le mardi 4 février 2025, 18:53:30 CET Slawomir Jaranowski a écrit : > > > > Hi, > > > > > > > > I will be working on compiler, install, deploy plugins to prepare and > > > > switch to GitHub issues ... > > > > > > > > First I will fix release-drafter configuration such we maintain two > > > > version > > > > - master for Maven 4.x > > > > - branch for Maven 3.x > > > > > > > > Probably I need disable jenkins on master due to missing Maven beta, > > > > rc installation on jenkins > > > > > > > > Finally I will prepare PR which enable GitHub issues > > > > > > > > Will be appreciated if someone else look at PR and result, if no I > > > > will simply merge as technical tasks > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > -- > > Sławomir Jaranowski > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
