As a fly on the wall here, not a dev, I think a kinder view would reinterpret Maven's position not as "ridiculous" but rather "down-priority", as in "we are busy, we like fixing bugs, adding features, and scheduling things is not as important, otherwise this would turn into a real job ;-)"
Gary On Tue, Dec 19, 2023, 12:20 AM Alexander Kriegisch <alexan...@kriegisch.name> wrote: > Karl Heinz, > > my thoughts on your reply: > > > Maven 4.0.0 will be there when it's there. > > This is a totally valid statement, if this is the policy in the Apache > Maven project. No objections at all. > > But: > > > We are an open source project. We don't have a release timeline. > > That is suboptimal response, to say it politely. OpenJDK and Eclipse IDE > with dozens of simultaneously released components have release cycles > for 6 (OpenJDK) and 3 (Eclipse SimRel) months with defined dates for > certain phases like milestones, release candidates, general availability > dates. I.e., you can say "Maven does not have a release timeline", fine. > But giving the reason that you do not have one because Maven is OSS, is, > with all due respect, just ridiculous. > > Regards > -- > Alexander Kriegisch > https://scrum-master.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
