FWIW, a policy I would consider OK is something like "we support A and B actively and would only consider a release of C for a severe security CVE, but D is EOL and OB to further releases."
Gary On Sun, Feb 23, 2025, 09:25 Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > Given available developer time and the slow speed at which Maven > evolves, I'm not sure a generic policy is best. Practically we're not > really supporting 3.8.x now. I'd be OK with a policy stating, "We > support 3.9 and no other versions." That's not necessarily what we > want but it is what we do. > > When 4.0 is released, we change that to "We support 3.9 and 4.0." As > time marches on, we add and remove numbers to match what we're really > doing. > > On Sun, Feb 23, 2025 at 10:36 AM Hervé Boutemy <herve.bout...@free.fr> > wrote: > > > > or just keep the policy as we have, as it has been wisely worded: once 4 > will > > be GA, 3.8 will de-facto be EOL'ed as per policy intent > > > > no need to change policy, the currently one perfectly does the job: > > https://maven.apache.org/docs/history.html > > > > Reagrds, > > > > Hervé > > > > Le dimanche 23 février 2025, 09:12:21 CET Anders Hammar a écrit : > > > I think we should start by declaring maven 3.8.x EOL in preparation for > > > maven 4. > > > > > > /Anders > > > > > > On Sat, Feb 22, 2025 at 12:57 PM Matthias Bünger > > > <runningj...@web.de.invalid> > > > wrote: > > > > Hi, > > > > during the last days / weeks the topic of (end of) support of Maven > and > > > > it's plugins came up several times in Slack. > > > > > > > > On the history page it is stated that we support the last two minor > > > > versions. Looking at the releases, there was only one regression / > small > > > > backport patch for Maven 3.8 about two months after Maven 3.9 was > > > > released. There wasn't any update for Maven 3.6 (or older) after the > > > > following minor version has been released. > > > > > > > > Some of the discussion participants in Slack also said that > literally we > > > > only support the last minor version. > > > > Taking in consideration that we already "struggle" of getting things > > > > done I would like to start a discussion about the following two > topics: > > > > > > > > 1) Declare Maven 3.8.x as EOL, especially as it requires Java 1.7. > Last > > > > release (3.8.8) on 2023-03-08. > > > > 2) Change our support policy to: "We support only last minor version, > > > > except when there was the release of a new major version. Then we > > > > continue to support the last minor version of the previous major > version > > > > for some more time too" ("some" not specificed on purpose). > > > > > > > > I personally think that in reality it does not make any real > difference, > > > > but it takes away some constraints and "pressure" for us. > > > > > > > > What do you think? > > > > > > > > -- > > > > Matthias > > > > > > > > P.S. I know that faster EOL of versions can result in problems for > teams > > > > in small-changing companies. At my work we got some tools, that still > > > > only support Java EE 6 and Java 8 while we don't get newer versions > > > > provided by ops... > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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 > > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
