THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
To provide a proper overview of what has changed within the current release, we need to update file RELEASE_NOTES.md in our release branch (rel/VERSION
).
Therefore it is required to perform the following steps.
- Go to the StreamPipes release overview the following repository and follow the instructions (https://github.com/apache/streampipes/releases)
- Click on
Draft a new release
- Select the target rel branch as target and create a new tag with a random name (we won't save this release for now)
- Click on
Generate release notes
- As a next step, click on
Release Notes
link below the heading. - As the final step, paste the changes at the top of the
RELEASE_NOTES.md
like below, commit and push the changes.
...
- dominikriemer/jira-to-issues)
- Copy the release notes printed to the console and insert it into the release notes
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). # [x.yy.z] <GENERATED RELEASE NOTES> |
...
Code Block | ||||
---|---|---|---|---|
| ||||
# Create a new rc folder in the SVN (https://dist.apache.org/repos/dist/dev/streampipes) # Create a new directory for the version (e.g., 0.69.0) and add release candidate (which is increased for every failed release), e.g., rc1. # The folder structure should look like this: - 0.69.0 - rc1 # Copy the following files into this folder (they can be found in streampipes/target/checkout/target: - RELEASE_NOTES.md - RELEASE_VALIDATION.md - README.md - The zip file (apache-streampipes-VERSION-incubating-source-release.zip) - The asc file (apache-streampipes-VERSION-source-release.zip.asc) - The sha512 file (apache-streampipes-VERSION-source-release.zip.sha512) # # Commit these changes to SVN. |
...