-
Notifications
You must be signed in to change notification settings - Fork 125
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
New release names in polkadot-sdk #800
Comments
Yes, we should definitely change our release name as well. As crates.io is now used by Parity and our users as well, we should probably add a crates.io release cycle as well. Are we doing something like that already? |
I have to say I'm not a big fan of the naming approach of parity. I find it very unclear how stable2407, stable2407-1 and stable2407-02 are related (for example stable2407-2 was released in September). Still I think for the branches it makes sense to use the same as parity. |
Idea from encointer: Use major version to indicate a new api-client release and minor for polkadot updates. E.g. 1.2.0 -> version 1 from api-client and version 2 of polkdaot. If polkadot updates and we follow, it will be released as 1.3.0. |
Yes, that's the general idea |
Then a concrete TODO to solve this issue would be:
Or should we wait with the version 1.0.0 for something specific? |
If we adapt the versioning approach I would increase the major version to prevent/reduce confusion when someone is updating |
See #809 |
polkadot-sdk
change to a different naming schema for their releases:https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-stable2407
We should look into what this means for us. Should we also change the naming of our releases and branches?
The text was updated successfully, but these errors were encountered: