Skip to content

Maven 3.8.x - EOL #842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Maven 3.8.x - EOL #842

wants to merge 1 commit into from
+21 −85

Conversation

@slawekjaranowski
Copy link
Member

As we announced in: https://lists.apache.org/thread/s3rlsf93lc84m7dob4stfdy8gr8o35bs
update documentation to according it.

@slawekjaranowski
Copy link
Member Author

Also mentioned at:

@michael-o
Copy link
Member

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

@michael-o
Copy link
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
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 approved these changes Jul 12, 2025
View reviewed changes
Copy link
Contributor

@Bukama Bukama left a comment

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
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.

slachiewicz
slachiewicz reviewed Jul 16, 2025
View reviewed changes
content/markdown/docs/history.md.vm
#end

The Apache Maven team maintains the last version of the last two series of GA releases.
The last release is currently ${current39xVersion}, the Apache Maven team project will currently maintain two core versions: **${current39xVersion}** and **${current38xVersion}**.
Copy link
Member

Choose a reason for hiding this comment

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

thats wrong - we should keep 2 latest versions 3.9.x and 4.x

Copy link
Member Author

Choose a reason for hiding this comment

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

  • as 4.x is in pre-release mode ... should be mentioned here?
  • where do we have information that we mention two latest version?

@slachiewicz slachiewicz mentioned this pull request Jul 17, 2025
Merged
@slachiewicz
Copy link
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.

@slawekjaranowski slawekjaranowski mentioned this pull request Jul 17, 2025
Open
elharo
elharo reviewed Jul 19, 2025
View reviewed changes
content/markdown/docs/history.md.vm

The Apache Maven team maintains the last version of the last two series of GA releases.
The last release is currently ${current39xVersion}, the Apache Maven team project will currently maintain two core versions: **${current39xVersion}** and **${current38xVersion}**.
The last release is currently **${current39xVersion}**, the Apache Maven team project will currently maintain one the latest core versions.
Copy link
Contributor

Choose a reason for hiding this comment

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

delete "one"

@slawekjaranowski
Copy link
Member Author

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

@michael-o
Copy link
Member

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

Very good. To users@ as well?

@slawekjaranowski
Copy link
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
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
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@elharo elharo elharo left review comments

@slachiewicz slachiewicz slachiewicz left review comments

@Bukama Bukama Bukama approved these changes

@hboutemy hboutemy Awaiting requested review from hboutemy

@cstamas cstamas Awaiting requested review from cstamas

@gnodet gnodet Awaiting requested review from gnodet

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@slawekjaranowski @michael-o @slachiewicz @elharo @Bukama