Am 2022-10-30 um 11:24 schrieb Slawomir Jaranowski:
niedz., 30 paź 2022 o 11:16 Michael Osipov <micha...@apache.org> napisał(a):
Am 2022-10-30 um 11:02 schrieb Slawomir Jaranowski:
Hi,
We solved 42 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12344367
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key
Staging repo:
https://repository.apache.org/content/repositories/maven-1819/
https://repository.apache.org/content/repositories/maven-1819/org/apache/maven/plugin-tools/maven-plugin-tools/3.7.0/maven-plugin-tools-3.7.0-source-release.zip
Source release checksum(s):
maven-plugin-tools-3.7.0-source-release.zip - SHA-512 :
7a208c35d273ebaca83fcd1dace1c255b3e805bb5765de675792c1ed6ccd5b5dd1beb6782003e9162e925fa8ca8354b54dde15f252f50c497bfe4274c97974e3
Staging site:
https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/
Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for at least 72 hours.
This is weird. It should have been 3.7.1. We burn versions when the vote
has been canceled.
3.7.0 - was never released as the last vote was canceled.
So I restarted a new vote ...
From release procedure [1]:
If the vote is unsuccessful, the process will need to be restarted. Be
sure to:
- drop your staging repository as described in Dropping a Repo.
- remove the release from the corresponding github release
https://github.com/apache/maven-project/releases
[1]
https://maven.apache.org/developers/release/maven-project-release-procedure.html#check-the-vote-results
Yet another thing we need to document which does not reflect reality :-(
I'd say that for the past 10 years we have burned versions along with
tags when the vote was canceled. You can see that for Maven 3.3.x
especially.
Rather have no docs than faulty ones :-(
Thanks for making this obvious.
M
