-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove old release script and workflows #3907
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👇 🎤
Kudos, SonarCloud Quality Gate passed! |
readme_release.md
Outdated
# HOW TO Release navitia | ||
|
||
## Versioning | ||
|
||
Our versionning is based on [Semantic Versionning](nhttps://semver.org/) | ||
* the **major** version is bumped in case of an API/interface change or **when a binarisation is needed**. | ||
* the **minor** version is bumped when functionnalities are backward compatible. | ||
* the **patch** version is bumped on a bug fix. | ||
|
||
## "Regular" release | ||
|
||
This lets the script decide if it's major or minor release. | ||
The decision is based on the data_version located in source/type/data.cpp | ||
See [CONTRIBUTING.md](CONTRIBUTING.md) for details on how data_version is managed. | ||
|
||
First have a look on github's repo at PRs about to be released https://github.com/hove-io/navitia/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc | ||
* Check that `not_in_changelog` and `hotfix` labels are correct and none is missing on PRs that are gonna be released | ||
* Check that titles are correct (clear, with the component impacted) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, I think we should keep it (almost) and just mention in the end that it's done on Github, not by script anymore.
I'm OK to do a PR on this if it's OK with you.
If not, it should be removed from
Line 71 in ea3dea7
Please follow instructions from [readme_release.md](readme_release.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in f71f5d5
IMO, we can now merge.
Not planning any additional work on the subject.
d7710a4
to
f71f5d5
Compare
Also minor typo change
f71f5d5
to
f7a75ce
Compare
looks good to me 👍 |
Kudos, SonarCloud Quality Gate passed! |
To merge after running the new workflow for a few days/weeks