Skip to content

Commit e798cbe

Browse files
committed
README.adoc: document the release process
Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
1 parent f16caf1 commit e798cbe

1 file changed

Lines changed: 21 additions & 0 deletions

File tree

README.adoc

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,3 +75,24 @@ To use the same server port across several re-runs of this script and
7575
ultimately of the `nit.sh` which actually sets up the environment, you
7676
can e.g. `export NUT_PORT=34930` (be careful to not use port `12345` which
7777
the Java debug bridge seems to use by default, at least in IntelliJ IDEA).
78+
79+
Releasing
80+
~~~~~~~~~
81+
82+
Follow the standard Maven release process:
83+
84+
mvn release:prepare
85+
86+
This should move the versions and `git tag` the result, build the artifacts
87+
and run tests, and `git push` the repository.
88+
89+
NOTE: There is currently no `mvn release:perform` to push the artifacts to
90+
some Internet repository.
91+
92+
To prepare tarballs (source, docs, binaries) for the NUT website or GitHub
93+
Releases attachment, `git checkout` the commit with exact (not `*-SNAPSHOT`)
94+
version and use the `make-tarballs.sh` script.
95+
96+
Finally, at https://github.com/networkupstools/jNut/releases/new draft a
97+
new release (choose tag, generate notes, attach tarballs and JAR/WAR files
98+
directly) and announce in nut-website::news.txt.

0 commit comments

Comments
 (0)