Hi, A little clarification on why I would like to do it ...
- try shared GitHub tools with multi-release plugin 4x and 3.x versions [1] - do first release based on GitHub issue - to have a lesson what should be updated in procedures [2] - give posiility to use GitHub issues by user with more used projects - we will have more feedback - get feedback from committers - how we can, should work with GitHub issues Coping issues from jira to GitHub can be done in any moment after enabling issues on GitHub if it is needed, requested by users or we need it to help working on issues. [1] https://github.com/apache/maven-gh-actions-shared [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=337676773#JIRAtoGitHubIssuesswitching-Procedures-Conventions-TODO On Tue, 4 Feb 2025 at 18:53, Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > > 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 > > -- > Sławomir Jaranowski -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
