search

jakartaee / messaging

Jakarta Messaging
https://eclipse.org/ee4j/messaging
Other
39 stars 32 forks source link

Set version to 3.0.1-SNAPSHOT #280

Closed dblevins closed 3 years ago

dblevins commented 3 years ago

Don't merge until our final release is approved and published.

pzygielo commented 3 years ago

With 568693 completed and https://repo.maven.apache.org/maven2/jakarta/jms/jakarta.jms-api/3.0.0/ published - can this PR continue?

arjantijms commented 3 years ago

Yes, it should continue indeed.

OndroMih commented 3 years ago

The next version should be 3.1.0 because we plan to do some minor API enhancements like repeating annotations as mentioned in the release plan.

arjantijms commented 3 years ago

The next version should be 3.1.0

Yes, but for admin reasons we typically merge the release branch into master, so that those branches don't show any missed commits.

But this PR is too troublesome with the failing ECA check, so let's close it.

OndroMih commented 3 years ago

I agree, this PR is not in a good shape. The 3.0.0 branch is already up to date with the master branch except the change from 3.0.0-SNAPSHOT to 3.0.1-SNAPSHOT which I think shouldn't even be added to the master branch. The master branch should directly jump to 3.1.0-SNAPSHOT instead.