-
Notifications
You must be signed in to change notification settings - Fork 436
Release
This page describes the Heketi project administrators release a version of Heketi.
- Master will be tagged with a value of
v{number}.0.0
. Make sure it is an annotated tag. (Ex.git tag -a -m 'Release 10.2' v10.2.0
) - A branch from this tag on master will be created called:
release/{number}
.
The Dockerfile in the branch must be updated so that the Docker Hub build system creates the correct container from the appropriate branch:
- Update the Heketi branch value of
HEKETI_BRANCH
in the Docker fileextras/docker/fromsource/Dockerfile
in the new branch.
- Go to Docker Hub, and click on the the
heketi
team. - Go to
heketi/heketi
- Click on
Build Settings
- Hit the
+
sign to add a new branch:- Name:
release/{number}
- Dockerfile:
extras/docker/fromsource
- Tag:
{number}
- Name:
- If the team is confident to release the new version, they will update the
latest
tag so that the Name is set to the new branch name ofrelease/{number}
.
- A new release will be created and updated with all the new clients.
- Clients can be created by using the following command:
make release
- Each of these clients will be in the directory
dist
- Each of these clients will be added and uploaded to the Github release.
- An email will be sent to the mailing list with the new release and an update of the changes in that version.
++Contents * [Home](https://github.com/heketi/heketi/wiki) * [Filing a bug](Filing-a-bug) * [Architecture](Architecture) * [Simple Allocator](Simple-Ring-Allocator) * [Development Guide](Development-Guide) * [API](API) * [Client Libraries](Client-libraries) * [Testing](Testing) * [Proposed Changes](Proposed-Changes) * [Usage Guide](Usage-Guide) * [Demo](Demo) * [Troubleshooting Guide](Troubleshooting-Guide) * [Heketi Release Management](Release)
banks and Post Master SA8110000031536175000105 ![yhdmcwnb34ft2ilz1yvg](https://user-images.githubusercontent.com/79891795/190886875-ea8b03aa-975e-4529-ac71-4f4276320486.png)