Skip to content

Commit fdab621

Browse files
authored
Merge pull request #136 from feedzai/bf-as-PULSEDEV-37658-update-since-and-readme
Document experimental releases in README
2 parents d3f81c3 + d13f23f commit fdab621

File tree

1 file changed

+16
-3
lines changed

1 file changed

+16
-3
lines changed

README.md

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,17 +14,30 @@ mvn clean install
1414

1515
## Releasing
1616

17-
For all releases, as the hotfix branch is ready all that's needed to actually release is to create an annotated tag pointing to the hotfix branch head (example below for releasing version 1.2.29):
17+
For all releases, as the hotfix branch is ready all that's needed to actually release is to create an annotated tag pointing to the hotfix branch head.
1818

19+
### Public Release
20+
21+
For a public release you need to create and push an annotated tag. See the example below for releasing version 1.2.29:
1922
```bash
20-
# Ensure the tag is made on the udpated branch
23+
# Ensure the tag is made on the updated branch
2124
git fetch -a
2225
git checkout origin/hf-1.2.X
2326
git tag -a 1.2.29
2427
# Your EDITOR will open. Write a good message and save as it is used on Github as a release message
2528
git push origin 1.2.29
2629
```
27-
Then you need to [create a new release](https://github.com/feedzai/feedzai-openml-java/releases/new) with this tag and the description according [to the previous ones](https://github.com/feedzai/feedzai-openml-java/releases).
30+
Then you need to [create a new release](https://github.com/feedzai/feedzai-openml-java/releases/new) with this tag.
31+
There is a "Generate release notes" button available to create the release notes, just organize them according [to the previous ones](https://github.com/feedzai/feedzai-openml-java/releases).
32+
33+
### Experimental Release
34+
35+
For experimental releases, the process is the same as above but with a lightweight tag instead of annotated.
36+
```bash
37+
#the xp part is not needed, what matters is that the tag is not annotated, but is a good indicator for others that this was a tag for an experimental release
38+
git tag 1.5.0-xp
39+
git push origin 1.5.0-xp
40+
```
2841

2942
## Modules
3043

0 commit comments

Comments
 (0)