This document guides every committer to release SkyWalking in Apache Way, and also help committers to check the release for vote.
Follow Apache maven deployment environment document to set gpg tool and encrypt passwords
Use the following block as a template and place it in ~/.m2/settings.xml
<settings>
...
<servers>
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
<username> <!-- YOUR APACHE LDAP USERNAME --> </username>
<password> <!-- YOUR APACHE LDAP PASSWORD (encrypted) --> </password>
</server>
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
<username> <!-- YOUR APACHE LDAP USERNAME --> </username>
<password> <!-- YOUR APACHE LDAP PASSWORD (encrypted) --> </password>
</server>
...
</servers>
</settings>
- Add your GPG public key into SkyWalking GPG KEYS file, only if you are a committer, use your Apache id and password login this svn, and update file. Don't override the existing file.
- Upload your GPG public key to public GPG site. Such as MIT's site. This site should be in Apache maven staging repository check list.
This step is only for test, if your env is set right, don't need to check every time.
./mvnw clean install -Pall (this will build artifacts, sources and sign)
./mvnw release:clean
./mvnw release:prepare -DautoVersionSubmodules=true -Pall
- Set version number as x.y.z, and tag as vx.y.z (version tag must start with v, you will find the purpose in next step.)
You could do a GPG sign before doing release, if you need input the password to sign, and the maven don't give the chance,
but just failure. Run gpg --sign xxx
to any file could remember the password for enough time to do release.
./mvnw release:perform -DskipTests -Pall
- The release will automatically be inserted into a temporary staging repository for you.
export RELEASE_VERSION=x.y.z (example: RELEASE_VERSION=5.0.0-alpha)
cd tools/releasing
sh create_source_release.sh
NOTICE, create_source_release.sh
is just suitable for MacOS. Welcome anyone to contribute Windows bat and Linux shell.
This scripts should do following things
- Use
v
+RELEASE_VERSION
as tag to clone the codes. - Make
git submodule init/update
done. - Exclude all unnecessary files in the target source tar, such as .git, .github, .gitmodules. See the script for the details.
- Do
gpg
andshasum 512
.
The apache-skywalking-apm-x.y.z-src.tgz
should be found in tools/releasing
folder,
with .asc, .sha512.
- Use ApacheId to login
https://repository.apache.org/
- Go to
https://repository.apache.org/#stagingRepositories
- Search
skywalking
and find your staging repository - Close the repository and wait for all checks pass. In this step, your GPG KEYS will be checked. See set PGP document, if you haven't done it before.
- Go to
{REPO_URL}/org/apache/skywalking/apache-skywalking-apm/x.y.z
- Download
.tar.gz
and.zip
with .asc and .sha1
- Use ApacheId to login
https://dist.apache.org/repos/dist/dev/skywalking/
- Create folder, named by release version and round, such as: x.y.z
- Upload Source code package to the folder with .asc, .sha512
- Package name: apache-skywalking-x.y.z-src.tar.gz
- See Section "Build and sign the source code package" for more details
- Upload distribution package to the folder with .asc, .sha512
- Package name: apache-skywalking-bin-x.y.z.tar.gz, apache-skywalking-bin-x.y.z.zip
- See Section "Find and download distribution in Apache Nexus Staging repositories" for more details
- Create .sha512 package:
shasum -a 512 file > file.sha512
Send an announcement mail in dev mail list.
Mail title: [ANNOUNCE] SkyWalking x.y.z test build available
Mail content:
The test build of x.y.z is available.
We welcome any comments you may have, and will take all feedback into
account if a quality vote is called for this build.
Release notes:
* https://github.com/apache/skywalking/blob/master/CHANGES.md
Release Candidate:
* https://dist.apache.org/repos/dist/dev/skywalking/xxxx
* sha512 checksums
- sha512xxxxyyyzzz apache-skywalking-apm-x.x.x-src.tgz
- sha512xxxxyyyzzz apache-skywalking-apm-bin-x.x.x.tar.gz
- sha512xxxxyyyzzz apache-skywalking-apm-bin-x.x.x.zip
Maven 2 staging repository:
* https://repository.apache.org/content/repositories/xxxx/org/apache/skywalking/
Release Tag :
* (Git Tag) x.y.z
Release CommitID :
* https://github.com/apache/skywalking/tree/(Git Commit ID)
* Git submodule
* skywalking-ui: https://github.com/apache/skywalking-rocketbot-ui/tree/(Git Commit ID)
* apm-protocol/apm-network/src/main/proto: https://github.com/apache/skywalking-data-collect-protocol/tree/(Git Commit ID)
* oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol https://github.com/apache/skywalking-query-protocol/tree/(Git Commit ID)
Keys to verify the Release Candidate :
* https://dist.apache.org/repos/dist/release/skywalking/KEYS
Guide to build the release from source :
* https://github.com/apache/skywalking/blob/x.y.z/docs/en/guides/How-to-build.md
A vote regarding the quality of this test build will be initiated
within the next couple of days.
Any PMC, committer or contributor can test features for releasing, and feedback. Based on that, PMC will decide whether start a vote.
Call a vote in [email protected]
Mail title: [VOTE] Release Apache SkyWalking version x.y.z
Mail content:
Hi All,
This is a call for vote to release Apache SkyWalking version x.y.z.
Release notes:
* https://github.com/apache/skywalking/blob/x.y.z/CHANGES.md
Release Candidate:
* https://dist.apache.org/repos/dist/dev/skywalking/xxxx
* sha512 checksums
- sha512xxxxyyyzzz apache-skywalking-apm-x.x.x-src.tgz
- sha512xxxxyyyzzz apache-skywalking-apm-bin-x.x.x.tar.gz
- sha512xxxxyyyzzz apache-skywalking-apm-bin-x.x.x.zip
Maven 2 staging repository:
* https://repository.apache.org/content/repositories/xxxx/org/apache/skywalking/
Release Tag :
* (Git Tag) x.y.z
Release CommitID :
* https://github.com/apache/skywalking/tree/(Git Commit ID)
* Git submodule
* skywalking-ui: https://github.com/apache/skywalking-rocketbot-ui/tree/(Git Commit ID)
* apm-protocol/apm-network/src/main/proto: https://github.com/apache/skywalking-data-collect-protocol/tree/(Git Commit ID)
* oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol https://github.com/apache/skywalking-query-protocol/tree/(Git Commit ID)
Keys to verify the Release Candidate :
* https://dist.apache.org/repos/dist/release/skywalking/KEYS
Guide to build the release from source :
* https://github.com/apache/skywalking/blob/x.y.z/docs/en/guides/How-to-build.md
Voting will start now (xxxx date) and will remain open for at least 72 hours, Request all PMC members to give their vote.
[ ] +1 Release this package.
[ ] +0 No opinion.
[ ] -1 Do not release this package because....
All PMC members and committers should check these before vote +1.
- Features test.
- All artifacts in staging repository are published with .asc, .md5, *sha1 files
- Source code and distribution package (apache-skywalking-x.y.z-src.tar.gz, apache-skywalking-bin-x.y.z.tar.gz, apache-skywalking-bin-x.y.z.zip)
are in
https://dist.apache.org/repos/dist/dev/skywalking/x.y.z
with .asc, .sha512 LICENSE
andNOTICE
are in Source code and distribution package.- Check
shasum -c apache-skywalking-apm-x.y.z-src.tgz.sha512
- Build distribution from source code package (apache-skywalking-x.y.z-src.tar.gz) by following this doc.
- Apache RAT check. Run
./mvnw apache-rat:check
. (No binary in source codes)
Vote result should follow these.
- PMC vote is +1 binding, all others is +1 no binding.
- In 72 hours, you get at least 3 (+1 binding), and have more +1 than -1. Vote pass.
- Move source codes tar balls and distributions to
https://dist.apache.org/repos/dist/release/skywalking/
.
> export SVN_EDITOR=vim
> svn mv https://dist.apache.org/repos/dist/dev/skywalking/x.y.z https://dist.apache.org/repos/dist/release/skywalking
....
enter your apache password
....
- Do release in nexus staging repo.
- Public download source and distribution tar/zip locate in
http://www.apache.org/dyn/closer.cgi/skywalking/x.y.z/xxx
. We only publish Apache mirror path as release info. - Public asc and sha512 locate in
https://www.apache.org/dist/skywalking/x.y.z/xxx
- Public KEYS pointing to
https://www.apache.org/dist/skywalking/KEYS
- Update website download page. http://skywalking.apache.org/downloads/ . Include new download source, distribution, sha512, asc and document links. Links could be found by following above rules(3)-(6).
- Add a release event on website homepage and event page. Announce the public release with changelog or key features.
- Send ANNOUNCE email to
[email protected]
,[email protected]
, the sender should use Apache email account.
Mail title: [ANNOUNCE] Apache SkyWalking x.y.z released
Mail content:
Hi all,
Apache SkyWalking Team is glad to announce the first release of Apache SkyWalking x.y.z.
SkyWalking: APM (application performance monitor) tool for distributed systems,
especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures.
This release contains a number of new features, bug fixes and improvements compared to
version a.b.c(last release). The notable changes since x.y.z include:
(Highlight key changes)
1. ...
2. ...
3. ...
Please refer to the change log for the complete list of changes:
https://github.com/apache/skywalking/blob/vx.y.z/CHANGES.md
Apache SkyWalking website:
http://skywalking.apache.org/
Downloads:
http://skywalking.apache.org/downloads/
Twitter:
https://twitter.com/ASFSkyWalking
SkyWalking Resources:
- GitHub: https://github.com/apache/skywalking
- Issue: https://github.com/apache/skywalking/issues
- Mailing list: [email protected]
- Apache SkyWalking Team