What problem does your feature solve?
The experimental_spec_shaking_v2 feature flag gates spec shaking v2 behaviour behind an opt-in flag in v25 ever since v25.2.0. Once it has been validated, it should be made the default and only behaviour, removing the need for users to opt in.
What would you like to see?
For the v26 major version:
- Remove the
experimental_spec_shaking_v2 feature flag.
- Make the spec shaking v2 behavior enabled by default.
- Add a
disable_spec_shaking_v2 feature flag that allows users to opt out if issues arise during the v26 period.
Depending on feedback received during v26, for v27:
- Remove the
disable_spec_shaking_v2 feature flag entirely.
- Make spec shaking v2 always on with no option to disable.
What alternatives are there?
- Keep the
experimental_spec_shaking_v2 opt-in flag, but this delays adoption.
- Skip the
disable_spec_shaking_v2 escape hatch and make it always on immediately in v26. This should be considered if the feedback during v25 is positive.
What problem does your feature solve?
The
experimental_spec_shaking_v2feature flag gates spec shaking v2 behaviour behind an opt-in flag in v25 ever since v25.2.0. Once it has been validated, it should be made the default and only behaviour, removing the need for users to opt in.What would you like to see?
For the v26 major version:
experimental_spec_shaking_v2feature flag.disable_spec_shaking_v2feature flag that allows users to opt out if issues arise during the v26 period.Depending on feedback received during v26, for v27:
disable_spec_shaking_v2feature flag entirely.What alternatives are there?
experimental_spec_shaking_v2opt-in flag, but this delays adoption.disable_spec_shaking_v2escape hatch and make it always on immediately in v26. This should be considered if the feedback during v25 is positive.