[ ] Go, Dotnet (Align Persistent Subscription naming and behaviour with RFC-022 - Align Persistent Subscription, we'll need to align ASAP before release.
[ ] For Persistent Subscription we'll use for now HTTP API then switch to server capabilities when it's available fully on the database. We'll need to have a fallback for HTTP API if the database version is below 21.10.1.
[ ] Persistent Subscription management is not part of MVT so it's not blocking, if we can get it within ~1 week then we shall wait, if not proceed with the release.
[ ] Use the same infrastructure at Changelog as for the main database repo in the next 2 weeks. We shall use GH releases with information from the changelog.
[ ] Implement ASAP on the clients the agreement concerning deadlines. [RFC] Standardize gRPC client deadlines
[ ] Go, Dotnet (Align Persistent Subscription naming and behaviour with RFC-022 - Align Persistent Subscription, we'll need to align ASAP before release.
[ ] For Persistent Subscription we'll use for now HTTP API then switch to server capabilities when it's available fully on the database. We'll need to have a fallback for HTTP API if the database version is below 21.10.1.
[ ] Persistent Subscription management is not part of MVT so it's not blocking, if we can get it within ~1 week then we shall wait, if not proceed with the release.
[ ] Use the same infrastructure at Changelog as for the main database repo in the next 2 weeks. We shall use GH releases with information from the changelog.
[ ] Start using Semver from this release.