niedz., 14 kwi 2024 o 06:59 Matthias Bünger <runningj...@web.de.invalid> napisał(a):
> Hi, > > a +0 from me as I'm not that long into the Maven projekt but the first > think that came to my mind when reading this: Then why not all? And if I > It is simple projects, where more of the historical and probably new issues will be about version updates. Other projects have a longer history, and we want to be supplier agnostic for more complicated projects, but it is another discussion not for this voting. > remember correctly there were causes why Maven uses the (partially) > locked JIRA as an issue tracker. > > Matthias > > Am 13.04.2024 um 15:55 schrieb Slawomir Jaranowski: > > Hi, > > > > Rationale: > > > > - more of changes in those projects are the dependencies updates make by > > the Dependabot, next we create issues in Jira by manual copy paste to > have > > a release notes > > - we can use Release Drafter for preparing release notes on GitHub - no > > manual works and easy to publish > > - release notes on GitHub are more easier to find > > - it is our internal project used in ASF > > > > Taks to do: > > > > - release next version ASF 32 / Maven 42 as is > > - make jira project MPOM - read only > > - leave current open issues in jira as is - with notes about migration - > if > > someone want to work on it, will copy it to GitHub > > - enable issues on GitHub > > - update project documentation > > > > If the vote passes - I will take care of it. > > > > Jira project: > > https://issues.apache.org/jira/projects/MPOM > > > > GitHub repositories: > > https://github.com/apache/maven-apache-parent > > https://github.com/apache/maven-parent > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski