[RESULT] [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
Hi, The vote has passed with the following result: +1 (binding): Sylwester Lachiewicz, Tamás Cservenák, Olivier Lamy, Slawomir Jaranowski +1 (non binding): zhongming hua, Enrico Olivelli +0 (non binding): Matthias Bünger PMC quorum: reached I will process tasks from voting. -- Sławomir Jaranowski
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 sob., 13 kwi 2024 o 15:55 Slawomir Jaranowski napisał(a): > 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 > > -- > Sławomir Jaranowski > -- Sławomir Jaranowski
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
sob., 13 kwi 2024 o 15:55 Slawomir Jaranowski napisał(a): > 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 > > -- > Sławomir Jaranowski > I will wait at least 7 days :-) for voting -- Sławomir Jaranowski
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 On Sat, 13 Apr 2024 at 11:56 PM, Slawomir Jaranowski wrote: > 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 > > -- > Sławomir Jaranowski >
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
niedz., 14 kwi 2024 o 06:59 Matthias Bünger 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
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
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 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
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 On Sat, Apr 13, 2024, 15:56 Slawomir Jaranowski wrote: > 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 > > -- > Sławomir Jaranowski >
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 sob., 13 kwi 2024, 15:56 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > 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 > > -- > Sławomir Jaranowski >
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 Enrico Il Sab 13 Apr 2024, 16:48 zhongming hua ha scritto: > +1 > I think generating release notes from the Github release drafter is > more convenient. > Can we close the project on Jira after we have resolved the remaining > issues? > > Best regards! > Zhongming Hua > > Slawomir Jaranowski 于2024年4月13日周六 21:56写道： > > > > 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 > > > > -- > > Sławomir Jaranowski > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 I think generating release notes from the Github release drafter is more convenient. Can we close the project on Jira after we have resolved the remaining issues? Best regards! Zhongming Hua Slawomir Jaranowski 于2024年4月13日周六 21:56写道： > > 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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
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 -- Sławomir Jaranowski
