...
Table of Contents | ||
---|---|---|
|
1. Create a gpg KEY
For those who are RM for the first time, this step needs to be carried out.
...
If you find that after the key is added "unverified" , remember to bind the email used in the GPG key to your github account (https://github.com/settings/emails )。
2. Ready to release version
(Note: Different projects may adopt different branch management methods, which are for reference only)
...
Then start the official release.
3.release version
3.1 Automatically tag on github and generate various signature files
...
$ git show release/0.8.1 --name-only
4 What if the vote fails
When the vote fails, the battlefield needs to be cleared first, and then reposted.
...
5. What to do after the vote is passed
After 72 hours of voting, a summary email should be made:
...
Panel |
---|
Theme:[VOTE] Release Apache IoTDB 0.9.0 Hello all, The vote will be passed if there is no -1 vote ( as there are 3 IPMC +1 votes already), but we still hope all other IPMCs vote for it. Please vote accordingly: |
6. What to do after the general list vote
First send a summary email to the general mailing list
...
Note: All apache mirrors will start synchronizing these files, which will usually be synchronized within 24 hours. After that, you can send a statement email.
7. Delete the old version of the release file
Apache seems to require that when the new versions are synchronized, delete the files of the old version (for example, 0.8.0-incubating in this example), but I checked several projects, this is not absolutely required. . It is recommended to keep some versions.
...
svn commit -m "Write commit log"
8. Officially release Maven files
Go to https://repository.apache.org/#welcome, log in to your account, then go to Staging Repositories to select the version you closed before and select release. Finished.
9. github publish release
Go to https://github.com/apache/incubator-iotdb/releases and change the previous this is a pre-release & save draft to publish release.
10. Update the code of the release branch to the latest
In our project, the release branch always points to the latest release version.
...
git merge -X theirs release/0.8.1
11. Update JIRA
Set the released version to "released" and set the "release-date"
Add the next version to the versions.
I do n’t have permission so I have n’t tested it yet
12. Update the download link on the official website
Website Directory:
https://github.com/apache/incubator-iotdb-website
...
Change the above version to your final version.
13. Tell the world!
After you confirm that most of the mirrors are synchronized, you can tell the world to release a new version of the information:
...
More reference examples:https://lists.apache.org/list.html?dev@iotdb.apache.org:gte=1d:announce
Publish Python package to Pypi
First, you must have an account, register here:https://pypi.org/account/register/
...
https://packaging.python.org/tutorials/packaging-projects/
Publish Docker image package to DockerHub
First, you need to have a username under the dockerhub website.
...