@dependabot rebase

@dependabot rebase

@dependabot rebase

@garydgregory Any ETA when you want to work on 2.0.0-M1? Like do you have something in mind when a first 2.x release (milestone or rc) will be likely to happen?
(I am aware of https://issues.apache.org/jira/projects/EMAIL/issues/EMAIL-203 and https://repository.apache.org/content/repositories/snapshots/ and https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-email/)

@mkurz
I can try for an M1 at the end of the week.

@mkurz I can try for an M1 at the end of the week.

Thanks! That would nice 😉

@garydgregory How is it going? Any ETA? No pressure, just asking what the current state is. Thanks for all your work!

@garydgregory How is it going? Any ETA? No pressure, just asking what the current state is. Thanks for all your work!

Within a week or two hopefully.

Hi any updates on this? Thanks

I hope to look within a week or two but I am maintaining other components ATM.

@garydgregory I see that you tagged https://github.com/apache/commons-email/releases/tag/commons-email-2.0.0-M1-RC1, however where can I find this release?

• https://repository.apache.org/content/repositories/releases/org/apache/commons/commons-email/ ?
• https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-email/ there is only 2.0.0-M1-SNAPSHOT from december...

thanks!

Hello @mkurz
You found the tag for the Release Candidate 1 (RC1). The vote is open for 3 days, if it passes, then the RC will be promoted.

Hello @mkurz You found the tag for the Release Candidate 1 (RC1). The vote is open for 3 days, if it passes, then the RC will be promoted.

Really appreciate your work, however, is there any update on the releases? Thanks

Hello @glau2
The release vote is still in progress. Thank you for your patience.

@garydgregory I see that the artifact id changed to commons-email2-*, was this on purpose?
See: https://repo1.maven.org/maven2/org/apache/commons/

@mkurz ,
That would an odd change to do by accident 😉
We can't break binary compatibility within a major release line.

To be clear: if a release breaks binary compatibility, in Commons we change both the package name and the Maven co-ordinates.

Hi, just want to check if there is any progress/update on this?

Hello @glau2

Please use 2.0.0-M1.

Hi @garydgregory,
so M1 is on Maven Central since 2024-06-15 - when do you expect to move on to a RC or final release? Can you provide a (rough) timeline? Thanks!

Hello @mkurz
What has your testing revealed using 2.0.0-M1?

@garydgregory We switched a library we offer our framework users to 2.0.0-M1 and all our tests pass:

• Switch over dependencies to commons-email2 / Jakarta (WIP) playframework/play-mailer#342

Maybe I should push out a M1 as well so people can test that...

Maybe I should push out a M1 as well so people can test that...

Done: https://github.com/playframework/play-mailer/releases/tag/11.0.0-M1

FWIW I've gone ahead and deployed 2.0.0-M1 (via Play Mailer) and it's all working very nicely. Thanks for your work on this and look forward to a RC. 👍

@garydgregory Any ETA for RC or final release?

@garydgregory Any ETA for RC or final release?

?

@mkurz

I need to hear from folks (like you), that 2.0.0-M1 works for them. When 2.0.0 is out the API will be set in stone and no binary breaks will be allowed.

Did you advertise the M1 somehow/somewhere?

All release are posted on the Commons mailing lists and the Apache-wide announce mailing lists.

Hi @mkurz the RIPE NCC DB team have been using 2.0.0-M1 in production (https://github.com/RIPE-NCC/whois/) since last September with no issues. We handle about 30K outgoing mails per day, and maybe a few hundred replies including Delivery Status Notifications. So can confirm it works for us. Thank you to the commons-email team for your work!

Awesome @eshryane, thanks for confirming!

Hi, is there any ETA for final release ?
i see it has been discussed in
https://lists.apache.org/thread/prgf2m77oqwvbhgtzgry6h9x7pw5oz1d as well and no progress then.
We are not allowed to use Milestone, RC versions in production and we need release version. Should we consider to switch to another library instead of waiting for an additional year.
For now, we are just interested for the estimated release date for the library with jakarta supported release.
Thank you

Can you at least test the current version and report any issue?

Thanks for responding.
We are using / testing it in our test environment and looks fine until now. We use it mostly for email parsing and no visible issues until now.
Instead of having this kind of long waiting time for the release, can't you release it and create hotfix/bugfix versions if needed ?

@ramazangirgin-check24

Thank you for checking the current release in your environment.

There is no "just" doing a release, it's not a push a button operation. Creating a release is not a free exercise, it takes a release manager to do the work and then at least 2 other people to review the release candidate. The main issue here though is that this is a new major release, and once out, it means the API is set in stone since we are serious about binary compatibility, no jar hell wanted. We want to make sure the API is right, and that likely takes more reviewing so we don't handcuff ourselves. Now, it's possible the API is fine as it is, but I'm not 100% sure.

garydgregor

Thank you for the answer. We will be waiting for the release version, hoping it will be released soon. Thanks in advance.

Superseded by #362.

@garydgregory It is more than one year now since 2.0.0-M1. What's your feeling about an RC or what do you think are the next steps?

The superceding PR #362 was also closed

What's the plan here?

Hello @mkurz

Are you using 2.0.0-M1?

Are you using 2.0.0-M1?

No...

Then you should 😉 We don't want to break binary compatibility within the 1.x release line.

You have any stats about downloads for that m1 artifact(s)?

It's very hard to get stats beyond what Maven Central and other public repos provide. No one can see what happens in Maven repositories that are inside corporate intranets. For example, companies use Nexus or Artifactory to cache everything form world at large, which is standard practice.