Our last mlkem-native release has been over seven months ago and we have seen 449 commits to the main branch, many of which bring major improvements and other changes.
We have been considering additional releases in between, but to me it always felt like that there was just this one last feature that we still need to add before we are ready to release. With this approach it seems, we will never have another release.
I thus propose, that we instead switch to regular releases. For example, we could release every 3 months starting in next month, i.e., releases in February, May, August, November. We could either set a fixed date, but it is probably fine to aim for the middle of the month and merge no later than the end of the month.
I propose that we keep major + minor releases of mlkem-native and mldsa-native in sync as they share a lot of configuration options and other features. The next releases would then likely be v1.1.0 for mlkem-native and v1.1.0-alpha for mldsa-native. At some point the -alpha will be dropped for mldsa-native once we are sufficiently confident that APIs and configuration is stable.
After the next release is out, we probably want to start maintaining a CHANGELOG.md or similar to keep track of significant changes that should make it to the release notes.
To keep this sync, we'll have to freeze changes that would require changes in the other repository in the days prior to a release or merge them at the same time.
@hanno-becker, what do you think?
Our last mlkem-native release has been over seven months ago and we have seen 449 commits to the main branch, many of which bring major improvements and other changes.
We have been considering additional releases in between, but to me it always felt like that there was just this one last feature that we still need to add before we are ready to release. With this approach it seems, we will never have another release.
I thus propose, that we instead switch to regular releases. For example, we could release every 3 months starting in next month, i.e., releases in February, May, August, November. We could either set a fixed date, but it is probably fine to aim for the middle of the month and merge no later than the end of the month.
I propose that we keep major + minor releases of mlkem-native and mldsa-native in sync as they share a lot of configuration options and other features. The next releases would then likely be
v1.1.0for mlkem-native andv1.1.0-alphafor mldsa-native. At some point the-alphawill be dropped for mldsa-native once we are sufficiently confident that APIs and configuration is stable.After the next release is out, we probably want to start maintaining a
CHANGELOG.mdor similar to keep track of significant changes that should make it to the release notes.To keep this sync, we'll have to freeze changes that would require changes in the other repository in the days prior to a release or merge them at the same time.
@hanno-becker, what do you think?