On Wed, 8 May 2024 at 17:04, Tamás Cservenák <ta...@cservenak.net> wrote: > > Howdy, > > Olivier, I find this quite interesting, that according to you doing an > Eclipse release (even M one) is "just push a few buttons and run > something for a minute". > On the other hand, on Slack you educate Christoph about the "Apache way". > Please calm down and remain respectful.
As I said, I tried to search for any process or vote with the last release, and I could not find anything. That's why it's my conclusion. By the way, I cannot see anything non-respectful in the approach about trying to figure out how a major piece of our stack is managed. > > Your PR [1] has been reviewed by Sisu project lead (Stuart McCulloch) and > is merged. All is fine. > > The problem is in the "release must happen RIGHT NOW" stance of yours (for > whatever reason). > No Sisu committer will or can throw away everything they currently do (or > planned to do), just to make Sisu release happen, as you ask for it. > We are doing our best, and release for sure will happen soonish, as there > are several merged, but also several ongoing changes to be done yet (see > open PRs). > > [1] https://github.com/eclipse/sisu.plexus/pull/52 > > On Wed, May 8, 2024 at 7:55 AM Christoph Läubrich <m...@laeubi-soft.de> > wrote: > > > Hi Olivier, > > > > I'm not 100% sure about the sisu[1] problem at Eclipse BUT usually there > > is no need for a vote or similar but from tiem to time there is a > > release or progress review. If I look here > > https://projects.eclipse.org/projects/technology.sisu/who you have 100% > > commits over the last three month, so it would make sense that @Konrad > > Windszus or @cstamas simply start a committer vote to make you a > > committer of the project, after that I would (if Stuart is non > > responsive anymore) start a Project Lead election for either any of you, > > at that point you then can do what ever is required (even though any > > committer can technically perform a release or ask for a release review > > some actions might require a Project Lead approval e.g. pushing to > > central), if you have any questions regarding Eclipse process you can > > ask the Eclipse EMO (e...@eclipse.org added as CC). > > > > If you need any help I can offer to give some help from my experience in > > other Eclipse Projects, at a first glance looking at the release page[1] > > a release review seems overdue but I'm not an expert on this specific > > topic, it just wont hurt to schedule one just to be sure. > > > > HTH > > Christoph > > > > [1] https://projects.eclipse.org/projects/technology.sisu > > [2] https://projects.eclipse.org/projects/technology.sisu/governance > > > > Am 07.05.24 um 23:23 schrieb Olivier Lamy: > > > Hi, > > > Sure but as a long-term developer, I cannot release this plexus part > > anymore. > > > It used to be very easy to release this major part of the system (but > > > for some reason this has been moved somewhere else. not something to > > > discuss again, of course) > > > I have been asking sisu dev mailing list for a release, but no answer > > yet. > > > I have been looking at this project mailing list archive. > > > There is an email about a possible process > > > (https://www.eclipse.org/lists/sisu-dev/msg00116.html), but as far as > > > I can see, this 0.9.0.M2 release has been done without any voting > > > process etc. > > > So releasing looks to be only a matter of having a few minutes to run > > > m-release-p and publish. (being contributor to another Eclipse > > > project, I cannot see anything with vote mandatory). > > > > > > If it's easier we can certainly move this sisu plexus project back to > > > where it was few years ago under the groupId org.codehaus.plexus and > > > releasing will not be a problem for maven contributors. > > > > > > regards > > > Olivier > > > > > > > > > On Mon, 6 May 2024 at 20:16, Tamás Cservenák <ta...@cservenak.net> > > wrote: > > >> > > >> Btw, I feel really strange to have to explain to a long term maven > > >> contributor, that he can do maven release whenever he feels so.... > > >> > > >> T > > >> > > >> On Mon, May 6, 2024 at 11:59 AM Tamás Cservenák <ta...@cservenak.net> > > wrote: > > >> > > >>> Howdy, > > >>> > > >>> I think you reversed the question... 3.9.7 was done and ready to go > > until > > >>> you stepped in. > > >>> > > >>> IMHO the real question is: > > >>> Is your issue (using overloaded methods in mojo config) really so > > urgent > > >>> to halt 3.9.7 release? > > >>> What is the problem with doing 3.9.8 maybe even two weeks later? > > >>> > > >>> > > >>> Thanks > > >>> T > > >>> > > >>> On Mon, May 6, 2024 at 7:45 AM Olivier Lamy <ol...@apache.org> wrote: > > >>> > > >>>> Is 3.9.7 really so urgent? > > >>>> Maybe we can wait a couple of days. > > >>>> I have been asking the sisu dev mailing list for a release. > > >>>> This should not be too long. > > >>>> I can see you are in the committers list > > >>>> (https://projects.eclipse.org/projects/technology.sisu/who) with > > >>>> Konrad so maybe you can help to expedite this? > > >>>> > > >>>> regards > > >>>> Olivier > > >>>> > > >>>> > > >>>> On Sun, 5 May 2024 at 21:05, Tamás Cservenák <ta...@cservenak.net> > > wrote: > > >>>>> > > >>>>> Howdy, > > >>>>> > > >>>>> Maven 3.9.7 was ready to be released 3 days ago and contains multiple > > >>>> fixes > > >>>>> contributed by non committers. > > >>>>> > > >>>>> MNG-8116 was added 2 days ago. I really see no reason to be blocked, > > to > > >>>>> "stop and wait" for a bugfix, as we can always spin 3.9.8. > > >>>>> Releases are cheap, and can be done whenever we (anyone of us) feels > > >>>> right > > >>>>> to do so... > > >>>>> > > >>>>> 3.9.7 is not the "last Maven 3.9.x" or anything like that, to have a > > >>>> "now > > >>>>> or never" situation. Just spin 3.9.8 whenever you think is ready. > > >>>>> > > >>>>> My 5 cents > > >>>>> T > > >>>>> > > >>>>> On Sun, May 5, 2024 at 2:14 AM Olivier Lamy <ol...@apache.org> > > wrote: > > >>>>> > > >>>>>> Hi > > >>>>>> Can we please integrate > > >>>> https://issues.apache.org/jira/browse/MNG-8116 > > >>>>>> The fix is ready and really simple. > > >>>>>> > > >>>>>> thanks > > >>>>>> Olivier > > >>>>>> > > >>>>>> On Wed, 24 Apr 2024 at 07:12, Tamás Cservenák <ta...@cservenak.net> > > >>>> wrote: > > >>>>>>> > > >>>>>>> Howdy, > > >>>>>>> > > >>>>>>> This is just a short newsflash about upcoming planned releases > > >>>> related to > > >>>>>>> Maven. > > >>>>>>> > > >>>>>>> Recently we got a huge spike in plugin releases, with various fixes > > >>>> and > > >>>>>>> improvements. I will not enumerate all of them here, just use `mvn > > >>>>>>> versions:display-plugin-updates` to pick them up ;) > > >>>>>>> (and more plugins to come). > > >>>>>>> > > >>>>>>> What I do want to share is about our upcoming Maven releases... > > >>>>>>> > > >>>>>>> Maven 3.9.7 is nearing (read: coming soon), and will have an > > >>>> important > > >>>>>>> Resolver update and other important fixes. Most importantly, the > > >>>>>> file-locks > > >>>>>>> are getting nice improvement (feedback VERY welcome). > > >>>>>>> > > >>>>>>> Maven 3.9.7 issues: > > >>>>>>> > > >>>>>> > > >>>> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.7 > > >>>>>>> > > >>>>>>> Resolver 1.9.19 issues (mostly bug fixes): > > >>>>>>> > > >>>>>> > > >>>> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.19 > > >>>>>>> > > >>>>>>> At the same time, we plan to release Maven Daemon (m39) as well, to > > >>>> have > > >>>>>> it > > >>>>>>> aligned with Maven 3,9,7: with many bug fixes and > > >>>> improvements/alignments > > >>>>>>> to "how Maven 3 behave". Our goal is to make the two (mvn and mvnd) > > >>>>>>> interchangeable on workstations. > > >>>>>>> > > >>>>>>> Next, Maven 4 is turning beta, so the next release will be beta1! > > >>>> And > > >>>>>>> again, same thing for Maven Damon (m40), we will have a release > > >>>> that will > > >>>>>>> include Maven 4 beta-1. > > >>>>>>> > > >>>>>>> Maven 4 beta-1 > > >>>>>>> > > >>>>>> > > >>>> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%204.0.0-beta-1 > > >>>>>>> > > >>>>>>> Resolver 2.0.0 (currently alpha-11, will become beta after Maven4 > > >>>> beta-1 > > >>>>>>> release): > > >>>>>>> > > >>>>>> > > >>>> > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%202.0.0-alpha-11 > > >>>>>>> > > >>>>>>> Keep your eyes on our upcoming releases, > > >>>>>>> and have fun! > > >>>>>>> - The Apache Maven team > > >>>>>> > > >>>>>> > > --------------------------------------------------------------------- > > >>>>>> 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 > > >>>> > > >>>> > > > > > > --------------------------------------------------------------------- > > > 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 > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
