Hi Divij,

Some of these are launch checklist items (not really goals) and some are
compatibility guarantees. More below.

On Thu, Jul 27, 2023, 12:10 PM Divij Vaidya <divijvaidy...@gmail.com> wrote:

> Hey Satish
>
> Could we consider adding "launch goals" in the release plan. While
> some of these may be implicit, it would be nice to list them down in
> the release plan. For this release, our launch requirements would be:
> 1. Users should be able to upgrade from any prior Kafka version to this
> version.
>

This is part of the compatibility guarantees. The upgrade notes mention
this already. If there is a change in a given release, it should definitely
be highlighted.

2. On release, this version (or it's dependencies) would not have any
> known MEDIUM/HIGH CVE.
>

This is a new policy and the details should be discussed. In particular,
the threshold (medium or high).

3. Presence of any "early access"/"beta" feature should not impact
> other production features when it is not enabled.
>

This is a general guideline for early access features and not specific to
this release. It would be good to have a page that talks about these things.

4. Once enabled, users should have an option to disable any "early
> access"/"beta" feature and resume normal production features, i.e.
> impact of beta features should be reversible.
>

This needs discussion and I don't think it's reasonable as a general rule.
For example, Kraft early access wasn't reversible and it was not feasible
for it to be.

5. KIP-405 will be available in "early access"/"beta" mode. Early
> access/beta means that the public facing interfaces won't change in
> future but the implementation is not recommended to be used in
> production.


I don't think it's ok to make this a requirement. Early access is a way to
get early feedback and all types of changes should be on the table. They
would be discussed via KIPs as usual. I believe there were some
incompatible changes for Kraft during the early access period although the
team aimed to minimize work required during upgrades. I have mentioned
Kraft a couple of times since it's a good example of a large feature that
went through this process.

Ismael

Reply via email to