Basically I’m looking for a guaranteed *minimum* amount of time for
users to be able to react to breaking changes. Considering the long
release cycles in place at many organizations, I think 6 months is
the absolute minimum.
Fully agree that 6 months as a minimum makes sense. Perhaps we can
make *that* the guideline? A deprecated piece of code will be removed
in a major release that is at least 6 months out from the moment of
deprecation?
I’m okay not including such an indication. I think it’s okay to take
things out of Beta in minor releases if we feel they’re ready. It’s
an addition and not a change so no danger of breaking anyone.
Works for me, too. That would then be something like:
"Beta methods and classes can be promoted to non-beta status in major
or minor releases. Removing beta functionality will only happen in
major releases (e.g. MAJOR.0)"
?
ap
