Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There should be one item in the list containing the just uploaded files. Click on "Close" and enter a message (e.g., Close StreamPipes release VERSION) and then you are done on the Maven side!


Revert Release

Important! Only when there was an error in the release. If this is the case, the maven release can be reverted with the following commandsThe final step is to upload the source release artifacts to the Apache SVN:

Code Block
languagebash
titleUpload files to SVN
# CreateDrop aartifacts newin rcNexus folderrepository
- inGo theto SVN (https://distrepository.apache.org/repos/dist/dev/incubator/streampipes/core/)
# 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 incubator-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
- The sha512 file

# Commit these changes to SVN.

Great! StreamPipes is ready for release voting.

Revert Release

 and login
- Go to "Staging Repositories" and search for "streampipes"
- There should be one item in the list containing the just uploaded files
- Click on "Drop" and enter a message

# Delete git tags, both locally and remote
- git tag -d release/#RELEASE_VERSION (e.g. git tag -d release/0.69.0)
- git push --delete origin release/#RELEASE_VERSION (e.g. git push --delete origin release/0.69.0)

# Rollback maven version
- mvn versions:set -DnewVersion=#OLD_DEVELOPMENT_VERSION (e.g. mvn versions:set -DnewVersion=0.60.0-SNAPSHOT
- Check that the version was changed correctly in all pom.xml files
- mvn versions:commit

# Commit changes in git
# Now the release process can be started again



The final step is to upload the source release artifacts to the Apache SVNImportant! Only when there was an error in the release. If this is the case, the maven release can be reverted with the following commands:


Code Block
languagebash
titleUpload files to SVN
# Create Dropa artifactsnew inrc Nexusfolder repository
-in Gothe toSVN (https://repositorydist.apache.org and login
- Go to "Staging Repositories" and search for "streampipes"
- There should be one item in the list containing the just uploaded files
- Click on "Drop" and enter a message

# Delete git tags, both locally and remote
- git tag -d release/#RELEASE_VERSION (e.g. git tag -d release/0.69.0)
- git push --delete origin release/#RELEASE_VERSION (e.g. git push --delete origin release/0.69.0)

# Rollback maven version
- mvn versions:set -DnewVersion=#OLD_DEVELOPMENT_VERSION (e.g. mvn versions:set -DnewVersion=0.60.0-SNAPSHOT
- Check that the version was changed correctly in all pom.xml files
- mvn versions:commit

# Commit changes in git
# Now the release process can be started again/repos/dist/dev/incubator/streampipes/core/)
# 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 incubator-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
- The sha512 file

# Commit these changes to SVN.


Great! StreamPipes is ready for release voting.

Initiate vote

Now comes the best part: You're ready to send the VOTE mail to the developer list!

...