This process describes the pre-release steps: 

Pre-release process

General Tasks

Agree on upcoming release

At some point in time, some member of the community thinks that it is time for a new release. If you think so, write an email to the dev@streampipes.apache.org list and ask if there is consensus on performing the next release.

Appoint release manager

Every release must have a release manager. Following up the agreement, some member of the Apache StreamPipes PPMC needs to volunteer as a release manager (RM). Usually, this is done by replying to the previous email on the upcoming release.

Agree on feature set for next release

Once a release manager has been found, the community discusses features that are not yet finished but should be part of the next release.

Prepare release testing

Create test checklist

To track things that have been tested by community members, a checklist can be used to indicate things that work or do not work.

Create a new checklist by copying the template from Pre-Release Checklist to a new page that indicates the next release version.

Setup release branches

Now it's time to 

Prepare test setup

Perform technical release readiness assessment

Checkout release branches

Setup test environment

Test system

Fix critical issue

Cherry-pick branches into dev

Perform legal release readiness assessment

Checkout release branches

Perform legal checks

Fix legal issue

Cherry-pick branches into dev