Skip to content
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

Update release docs #708

Merged
merged 1 commit into from
Apr 4, 2019
Merged

Update release docs #708

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 7 additions & 26 deletions doc/development/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,13 @@ You are not required to sign SNAPSHOT builds. Issue the following
command to deploy a SNAPSHOT.

```
$ mvn deploy
$ mvn clean deploy
```

## Release Commands

```
$ mvn release:prepare
$ mvn release:clean release:prepare
```

You will be asked a series of questions regarding version numbers. It
Expand All @@ -74,29 +74,10 @@ To perform a release, issue the following command.
$ mvn release:perform
```

This will upload the artifacts to OSS Sonatype and will require you to sign the
build. There is a list of known keys that have been used to sign tagged JeroMQ
releases [here](public-keys.md).
This will upload the artifacts to OSS Sonatype and release to Maven Central in
one go, and will require you to sign the build. There is a list of known keys
that have been used to sign tagged JeroMQ releases [here](public-keys.md).

## Build Publishing
# Making an Announcement on the ZeroMQ Mailing list when it has been successfully synced.

Log into the OSS Nexus Repository located at: [OSS
NEXUS](https://oss.sonatype.org/).

Click `Staging Repositories` link located on the left
navigation.

(show picture)

Locate the latest entry with the profile `org.zeromq`. Ensure it's
from JeroMQ. In order to release the project to the Maven Central, you
first must close the staging repository.

(show picture)

It will take a minute to reflect that it has been closed. Once you can
see the status change, you may now queue the build to be mirrored to
the Maven Central.

Making an Announcement on the ZeroMQ Mailing list when it has been
successfully synced.
TODO: more info?
6 changes: 5 additions & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,10 @@
<version>2.5.3</version>
<configuration>
<tagNameFormat>v@{project.version}</tagNameFormat>
<autoVersionSubmodules>true</autoVersionSubmodules>
<useReleaseProfile>false</useReleaseProfile>
<releaseProfiles>release</releaseProfiles>
<goals>deploy</goals>
</configuration>
</plugin>
<plugin>
Expand Down Expand Up @@ -282,7 +286,7 @@
</build>
</profile>
<profile>
<id>release-sign-artifacts</id>
<id>release</id>
<activation>
<property>
<name>performRelease</name>
Expand Down