Sitelet https://github.com/apache/maven-site/pull/842
Skip to content

Maven 3.8.x - EOL - #842

Merged
slawekjaranowski merged 1 commit into
apache:masterfrom
slawekjaranowski:mvn-3.8.x-eol
Nov 1, 2025
Merged

slawekjaranowski merged 1 commit into
apache:masterfrom
slawekjaranowski:mvn-3.8.x-eol

Conversation

@slawekjaranowski

@slawekjaranowski slawekjaranowski commented Jul 12, 2025 •

Copy link
Copy Markdown
Member

@slawekjaranowski

Copy link
Copy Markdown
Member Author

@michael-o

Copy link
Copy Markdown
Member

I will review later today since I thought about this before doing the release.

@michael-o

Copy link
Copy Markdown
Member

I think this is not enough. What we need to do is to advertise on dev@ and users@ that 3.8.x has reached its EOL and will be removed from the releases repository (ASF) and from the download page. This will give people time to react. I pretty much like how Apache Tomcat does this, they announce and then act a couple of months later. As we have seen as soon as it is removed from downloads.a.o it is unreachable. I don't want to break people stuff without letting them know first.
I think a sane date from would at least two months in the future, but if we calculate the summer vacation in 2025-10-03 is a good day since on a Friday less failures are expected.

WDYT?

@slawekjaranowski

Copy link
Copy Markdown
Member Author

I think this is not enough. What we need to do is to advertise on dev@ and users@ that 3.8.x has reached its EOL and will be removed from the releases repository (ASF) and from the download page. This will give people time to react. I pretty much like how Apache Tomcat does this, they announce and then act a couple of months later. As we have seen as soon as it is removed from downloads.a.o it is unreachable. I don't want to break people stuff without letting them know first. I think a sane date from would at least two months in the future, but if we calculate the summer vacation in 2025-10-03 is a good day since on a Friday less failures are expected.

WDYT?

Good idea, so, we first should send an email to dev, users , announce lists with information about plan:

  • remove from download page - documentation updates
  • remove from download.a.o
  • date of planed taks - like 2025-10-03 or even end of 2025-10

do you see any other steps?

@slawekjaranowski
slawekjaranowski marked this pull request as draft July 12, 2025 14:20

@Bukama Bukama left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree on the communication on ML before.

@michael-o

Copy link
Copy Markdown
Member

I think this is not enough. What we need to do is to advertise on dev@ and users@ that 3.8.x has reached its EOL and will be removed from the releases repository (ASF) and from the download page. This will give people time to react. I pretty much like how Apache Tomcat does this, they announce and then act a couple of months later. As we have seen as soon as it is removed from downloads.a.o it is unreachable. I don't want to break people stuff without letting them know first. I think a sane date from would at least two months in the future, but if we calculate the summer vacation in 2025-10-03 is a good day since on a Friday less failures are expected.
WDYT?

Good idea, so, we first should send an email to dev, users , announce lists with information about plan:

  • remove from download page - documentation updates
  • remove from download.a.o
  • date of planed taks - like 2025-10-03 or even end of 2025-10

do you see any other steps?

Yes, correct. My idea was first announce, two months later remove from the website and another month later from downloads.a.o. so end of Oct seems reasonable.

Comment thread content/markdown/docs/history.md.vm
@slachiewicz

Copy link
Copy Markdown
Member

We could remove old Maven versions from GH Ci right now to save time and resources.

About mail communication - we could simply say that it's EOL and will be removed from Apache dist downloads.
The proposed time looks good, but we could start removing references right after the announcement and only keep the dist area till the end.

Probably next question would be what is the minimal version of 3.9 that we support in plugin prerequisites.

Comment thread content/markdown/docs/history.md.vm Outdated
@slawekjaranowski

Copy link
Copy Markdown
Member Author

@michael-o

Copy link
Copy Markdown
Member

Message send: https://lists.apache.org/thread/gdyhw6mt6qhnbknpngpkj8s4ckx7s7xs

Very good. To users@ as well?

@slawekjaranowski

Copy link
Copy Markdown
Member Author

Message send: https://lists.apache.org/thread/gdyhw6mt6qhnbknpngpkj8s4ckx7s7xs

Very good. To users@ as well?

To: Maven Developers List <dev@maven.apache.org>, Maven Users List <users@maven.apache.org>
Cc: announce@maven.apache.org

@michael-o

Copy link
Copy Markdown
Member

Message send: https://lists.apache.org/thread/gdyhw6mt6qhnbknpngpkj8s4ckx7s7xs

Very good. To users@ as well?

To: Maven Developers List <dev@maven.apache.org>, Maven Users List <users@maven.apache.org>
Cc: announce@maven.apache.org

Perfect

@michael-o
michael-o removed their request for review August 2, 2025 21:38
@slawekjaranowski slawekjaranowski mentioned this pull request Oct 27, 2025
4 of 5 tasks
@slawekjaranowski

Copy link
Copy Markdown
Member Author

Time has elapsed last mail announcements, so we are ready to merge

@michael-o michael-o left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Make sure to remove from the distribution area. It will remain in the archive though.

@slawekjaranowski

Copy link
Copy Markdown
Member Author

LGTM. Make sure to remove from the distribution area. It will remain in the archive though.

From distribution area will be removed in next month ... according to info in email

@slawekjaranowski
slawekjaranowski marked this pull request as ready for review November 1, 2025 10:59
@slawekjaranowski
slawekjaranowski merged commit d4fcdbb into apache:master Nov 1, 2025
1 check passed
@slawekjaranowski
slawekjaranowski deleted the mvn-3.8.x-eol branch November 1, 2025 10:59
@michael-o

Copy link
Copy Markdown
Member

LGTM. Make sure to remove from the distribution area. It will remain in the archive though.

From distribution area will be removed in next month ... according to info in email

Very good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants