Yes! Assuming we're roughly following the "semantic versioning"
convention then here's what they say:
Given a version number MAJOR.MINOR.PATCH, increment the:
1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards
compatible manner, and
3. PATCH version when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available
as extensions to the MAJOR.MINOR.PATCH format.
So we'd still be able to to put out "patch" releases to 1.20 for any
urgent fixes.
On 2022/03/17 11:56, Vitalii Diravka wrote:
Does that mean we can merge the non backward compatible changes then, right?
Kind regards
Vitalii
On Mon, Mar 14, 2022 at 10:47 AM James Turton<dz...@apache.org> wrote:
Hi all
Does anyone have any objections to
https://github.com/apache/drill/pull/2490? Any reasons to do a 1.21.0
before a 2.0.0?
Regards
James
. I'
