Skip to content
This repository was archived by the owner on Feb 5, 2025. It is now read-only.

Conversation

@oguzkocer
Copy link
Contributor

In x.y.z version scheme, unless we are doing a hotfix, we want to increase the y value while creating a new beta/release. It looks like the current beta versions were incorrectly created for 2.2.1-beta.{version} instead of 2.3.0-beta.{version} which is minor mistake most of us have made.

While deciding on the final release version between 2.2.1 & 2.3.0, I thought it was more important to use the correct final release version than to stay consistent with the beta versions and decided to go with 2.3.0.

cc @jaclync @itsmeichigo (so you can keep this in mind for next beta versions)

@oguzkocer oguzkocer requested a review from a team August 19, 2022 16:01
@oguzkocer oguzkocer enabled auto-merge August 19, 2022 16:02
@oguzkocer oguzkocer merged commit 610a05e into trunk Aug 21, 2022
@oguzkocer oguzkocer deleted the release/2.3.0 branch August 21, 2022 20:42
@jaclync
Copy link
Contributor

jaclync commented Aug 22, 2022

Sorry @oguzkocer about not using the beta version following the x.y.z version scheme! I'll make sure to follow this in future work on any of our libraries.

@oguzkocer
Copy link
Contributor Author

No worries at all @jaclync - my note was just a reminder 🙂

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants