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

Update integration versioning #160

Open
Invictum opened this issue Aug 11, 2023 · 0 comments
Open

Update integration versioning #160

Invictum opened this issue Aug 11, 2023 · 0 comments

Comments

@Invictum
Copy link
Owner

Let's align integration versioning semantic to the real world things.
Currently versioning uses 3 digits semantics x.y.z (e. g. 1.6.2). I propose to keep it as is, but repurpose numbers meaning.
x - major version let align it with serenity-core version to make compatibility more transparent. E. g. version 2.x.x is compatible with Serenity 2.x, version 3.x.x is compatible with Serenity 3.x and so on.
y - minor version for updating report portal dependencies. E. g. change from 2.1.x to 2.2.x means RP dependency version was incremented both major or minor versions.
z - path version for new integration feature and bugfixes.

@Invictum Invictum created this issue from a note in Integration Revamp (In progress) Aug 11, 2023
@Invictum Invictum moved this from In progress to To do in Integration Revamp Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants