Skip to content
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

Merged
merged 2 commits into from
Mar 1, 2023
Merged

Remove old release script and workflows #3907

merged 2 commits into from
Mar 1, 2023

Conversation

pbench
Copy link
Contributor

@pbench pbench commented Jan 10, 2023

To merge after running the new workflow for a few days/weeks

Copy link
Contributor

@woshilapin woshilapin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👇 🎤

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Comment on lines 1 to 18
# 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)
Copy link
Contributor

@pbougue pbougue Jan 23, 2023

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

Please follow instructions from [readme_release.md](readme_release.md).
too.

Copy link
Contributor

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.

@pbougue
Copy link
Contributor

pbougue commented Feb 28, 2023

I rebased the PR (conflicting with #3931 as far as I saw).
A second check on the rebase is welcome @pbench 😉

@pbench
Copy link
Contributor Author

pbench commented Feb 28, 2023

looks good to me 👍

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@pbench pbench merged commit cf1d7c2 into dev Mar 1, 2023
@pbench pbench deleted the clean_workflows branch March 1, 2023 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants