@@ -15,7 +15,9 @@ <h1>Creating a new release</h1>
15
15
< li > Make sure there are no outstanding commits or
16
16
pull requests that should be in the new release.
17
17
< li > Do some testing.
18
- < li > Pick a release number < code > X.Y.Z</ code > .
18
+ < li > Pick a release number < code > X.Y.Z</ code >
19
+ where < code > X</ code > , < code > Y</ code > , and < code > Z</ code >
20
+ are numbers (no additional characters).
19
21
To stay consistent with
20
22
< a href ='https://semver.org '> Semantic Versioning</ a > ,
21
23
for now stay with < code > X=0</ code > .
@@ -26,31 +28,43 @@ <h1>Creating a new release</h1>
26
28
27
29
< li > In
28
30
< code > shasta/.github/workflows/Build.yml</ code > ,
29
- change the build id to < code > Shasta Release X.Y.Z</ code >
30
- in 4 places .
31
+ change < code > BUILD_ID </ code > to < code > Shasta Release X.Y.Z</ code >
32
+ in all < code > cmake </ code > commands (5 instances at the time of last update of this documentation) .
31
33
< li > Commit and push this change to trigger a new build on GitHub Actions.
32
34
Wait for that build to complete.
33
35
< li > Download the 7 artifacts. Unzip them and rename them to the following:
34
36
< ul >
35
37
< li > < code > shasta-Linux-X.Y.Z</ code >
36
38
< li > < code > shasta-OldLinux-X.Y.Z</ code >
37
- < li > < code > shasta-macOS-X.Y.Z</ code >
39
+ < li > < code > shasta-macOS-10.14-X.Y.Z</ code >
40
+ < li > < code > shasta-macOS-10.15-X.Y.Z</ code >
38
41
< li > < code > shasta-Ubuntu-16.04-X.Y.Z.tar</ code >
39
42
< li > < code > shasta-Ubuntu-18.04-X.Y.Z.tar</ code >
43
+ < li > < code > shasta-Ubuntu-20.04-X.Y.Z.tar</ code >
40
44
</ ul >
41
45
42
- < li > Create the release on GitHub and write some release notes.
43
- The release name should be just/simply < code > X.Y.Z</ code > .
46
+ < li > Create release notes in markdown format.
47
+ This is
48
+ < a href ="https://markdownlivepreview.com/ "> a web page</ a > that can be used to review
49
+ the release notes before posting on GitHub.
50
+ Just paste the markdown to the left pane.
51
+
52
+ < li > Create the release on GitHub and paste the release notes.
53
+ The release name should be just/simply < code > X.Y.Z</ code >
54
+ (no additional characters).
55
+ The release will not be visible to users until it gets published
56
+ two steps below.
44
57
< li > Upload the unzipped and renamed artifacts
45
58
to the new release as assets.
46
59
47
60
< li > Publish the release on GitHub.
48
61
< li > After the release has been published it should not be modified or deleted.
49
62
< li > In
50
63
< code > shasta/.github/workflows/Build.yml</ code > ,
51
- change the build id to
64
+ change < code > BUILD_ID </ code > to
52
65
< code > Shasta unreleased test build newer than release X.Y.Z</ code >
53
- in 4 places for future GitHub Actions builds.
66
+ in all < code > cmake</ code > commands for future GitHub Actions builds
67
+ (5 instances at the time of last update of this documentation).
54
68
</ ul >
55
69
56
70
0 commit comments