You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASING.md
+31-44Lines changed: 31 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,64 +18,51 @@ Also check if you can upgrade any dependencies:
18
18
make update-dependency-versions
19
19
```
20
20
21
-
## Make the release ##
21
+
## Decide what the next version should be ##
22
+
23
+
Versions follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html). To sum it up, it depends on what's changed (see `CHANGELOG.md`). Given a version number MAJOR.MINOR.PATCH:
22
24
23
-
In order to make releases secrets are required. Members of the core
24
-
team can install keybase and join the `cucumberbdd` team to access these secrets.
25
+
* Bump `MAJOR` when you make incompatible API changes:
26
+
* There are `Removed` entries, or `Changed` entries breaking compatibility
27
+
* A cucumber library dependency upgrade was major
28
+
* Bump `MINOR` when you add functionality in a backwards compatible manner:
29
+
* There are `Added` entries, `Changed` entries preserving compatibility, or
30
+
`Deprecated` entries
31
+
* Bump `PATCH` when you make backwards compatible bug fixes:
32
+
* There are `Fixed` entries
25
33
26
-
Remove the empty sections in the changelog. Don't commit these but run:
34
+
Display future version by running:
27
35
28
36
```
29
37
make version
30
38
```
31
39
32
-
Check if branch name and version are as expected.
40
+
Check if branch name and version are as expected. To change version run:
33
41
34
42
```
35
-
make release
36
-
```
43
+
mvn versions:set -DnewVersion=X.Y.Z-SNAPSHOT
44
+
```
37
45
38
-
#GPG Keys#
46
+
## Secrets ##
39
47
40
-
To make a release you must have the `[email protected]` GPG private key imported in gpg2.
48
+
Secrets are required to make releases. Members of the core team can install
49
+
keybase and join the `cucumberbdd` team to access these secrets.
41
50
42
-
```
43
-
gpg --import devs-cucumber.io.key
44
-
```
51
+
During the release process, secrets are fetched from keybase and used to sign
52
+
and upload the maven artifacts.
45
53
46
-
Additionally upload privileges to the Sonatype repositories are required. See the
47
-
[OSSRH Guide](http://central.sonatype.org/pages/ossrh-guide.html) for instructions. Then an
48
-
administrator will have to grant you access to the cucumber repository.
54
+
## Make the release ##
49
55
50
-
Finally both your OSSRH credentials and private key must be setup in your `~/.m2/settings.xml` -
0 commit comments