@@ -32,12 +32,7 @@ usually it's overall coverage above 80%)
32
32
33
33
The release is OK , once above is fullfilled to our satisfaction.
34
34
35
- 3) tag the build used for release so we can get back to it:
36
-
37
- git tag 0.XYZ
38
- git push origin --tags
39
-
40
- 4) produce proper distributions
35
+ 3) produce proper distributions
41
36
42
37
Check them before upload , always try to build on Solaris , since gnu tar might
43
38
create a non-standard compliant .tgz version and tag from step 0) will be used
@@ -71,25 +66,11 @@ number (0.12))
71
66
0.12.0.<k> ~ 0.12.0.1.<k>
72
67
...
73
68
74
- 5) Upload them using https://github.com/OpenGrok/OpenGrok/releases
75
-
76
- Note that the files has to be stored in a ZIP file for github to accept
77
- them so use incantation like follows:
78
-
79
- cd dist/
80
- ls -1 *.p5p *.pkg *.tar.gz | while read file; do
81
- echo $file | zip -0 -@ $file.zip;
82
- done
83
-
84
- Uploading from behing a proxy does not work so it is recommended to use
85
- direct internet connection.
86
-
87
- Also generate cryptographic digests for all the binaries ,
88
- e.g. using openssl:
69
+ 4) Create the release and upload the files via GitHub API:
89
70
90
- openssl dgst -sha256 <file1> <file2> ..
71
+ ./tools/dorelease.py -d -u <github_login> \
72
+ -D "some release description" \
73
+ -t <tag> dist/*.p5p dist/*.pkg dist/*.tar.gz
91
74
92
- and paste them next to the uploaded files.
75
+ Note: for pre-releases use the -P option
93
76
94
- Note that the files with packages have to be gzipped otherwise github
95
- upload does not allow them.
0 commit comments