Closed erikgb closed 3 months ago
I think v1 should be deplicate after releasing v2 or v2beta1.
Agree! Any more we want to adjust before v2 is finalized? I don't see anything missing from SubNamespace v2 API.
@erikgb I don't have anything else to add either. Everything looks good to me.
@erikgb I don't have anything else to add either. Everything looks good to me.
Should we just skip a beta-version of the API and go directly for v2? WDYT?
Should we just skip a beta-version of the API and go directly for v2? WDYT?
I think it's fine to skip beta and go directly to v2.
Should we just skip a beta-version of the API and go directly for v2? WDYT?
I think it's fine to skip beta and go directly to v2.
Thanks, I will do the work required. Marking this PR as a draft for now.
@zoetrope After making the v2 API served, ref. https://github.com/cybozu-go/accurate/pull/132, I think this PR is ready for review and eventual merge. Marking the types as deprecated also will help us identify code we need to migrate.
@zoetrope A gentle ping for a review of this PR. 🙏 I also have other open unreviewed PRs. 🙏 We prefer if a new release is cut as soon as possible. 🤠
@erikgb Sorry for the very late reply. I am planning to make a release. Can I release v1.4.0 after this PR is merged?
@erikgb Sorry for the very late reply. I am planning to make a release. Can I release v1.4.0 after this PR is merged?
@zoetrope Great! Would it be possible to include all open PRs before we cut the release? In particular, I would like to get https://github.com/cybozu-go/accurate/pull/142 in somehow.
The v2alpha1 version of the SubNamespace API has been available for a while, and I think it's time to consider deprecating the v1 version. The newer version has a much better observed state UX with conditions. We should probably make v2 (or v2beta1) available - to not "scare" our users from migrating (to an alpha version).