Skip to content

Commit 83845bf

Browse files
committed
Update release instructions
to point to new docs site and to Maven Central + about "releasing" the artifacts on Central Signed-off-by: marko-bekhta <marko.prykladna@gmail.com>
1 parent d77cf43 commit 83845bf

File tree

1 file changed

+6
-10
lines changed

1 file changed

+6
-10
lines changed

MAINTAINERS.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,9 @@ included in the distribution package.
5151
### Performing the release
5252

5353
Once you trigger the CI job, it automatically pushes artifacts to the
54-
[OSSRH repository manager](https://oss.sonatype.org/#stagingRepositories),
54+
[Maven Central](https://central.sonatype.com/),
5555
the distribution to [SourceForge](https://sourceforge.net/projects/hibernate/files/hibernate-validator/)
56-
and the documentation to [docs.jboss.org](https://docs.jboss.org/hibernate/validator/).
56+
and the documentation to [docs.hibernate.org](https://docs.hibernate.org/validator/).
5757

5858
* Transfer the released issues in JIRA to the "Closed state":
5959
* Go to [the list of releases](https://hibernate.atlassian.net/projects/HV?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page)
@@ -72,14 +72,10 @@ and the documentation to [docs.jboss.org](https://docs.jboss.org/hibernate/valid
7272
* **Be careful** when filling the form with the build parameters.
7373
* Note that for new branches where the job has never run, the first run will not ask for parameters and thus will fail:
7474
that's expected, just run it again.
75-
* Release the artifacts on the [OSSRH repository manager](https://oss.sonatype.org/#stagingRepositories).
76-
* Log into Nexus. The credentials can be found on Bitwarden; ask a teammate if you don't have access.
77-
* Click "staging repositories" to the left.
78-
* Examine your staging repository: check that all expected artifacts are there.
79-
* If necessary (that's very rare), test the release in the staging repository.
80-
You can drop the staging repo if there is a problem,
81-
but you'll need to revert the commits pushed during the release.
82-
* If everything is ok, select the staging repository and click the "Release" button.
75+
* If the release option `RELEASE_PUBLISH_AUTOMATICALLY` was selected as `false`-- release the artifacts on the [Maven Central portal](https://central.sonatype.com/).
76+
* Log into Maven Central. The credentials can be found on Bitwarden; ask a teammate if you don't have access.
77+
* Click on the profile circle at the top right and pick "View Deployments".
78+
* Find your deployment on the left and click "Publish".
8379

8480
### Announcing the release
8581

0 commit comments

Comments
 (0)