-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIzBAEBCgAdFiEE8osu2CcCCF5douGQu8PBaGu5w1EFAl26p+EACgkQu8PBaGu5
w1Fy+w//aS5d6PYmALndO9fnd2FfSrQXI12ZylEgli2SWZYkwnxeza+dNWAS0tkF
iG2xWVZ7DCLzdkvzwn9YUyBZ2DXDP6KOaLjWjxbKdLqggWxV/faaihUcnMtcrIDO
YkEe/k0GRDW0QuIW43pckdFJb8/dYyxEnB8xeWTzMOm2w4Cq6/wEKkgVI7HJDPCT
teXV+URjEqE/S0erxwUspy78p22st6n/oMUxQKTWQEcynmWOEiDwB2/szMVIn5EN
OJIN/lgg3EM+sUlfNRP6JyW+2fwvViWWMvJ5RhHBWDtaYnuJtUeE1hM6VUnR3kt2
yhYzwjtO8EKJN4LOPJpiSW+y0TFQMPL9o1kVd6jaX7PGNAU7fAOr8asxhZQ0iEA/
W16+fKPh17vw2kZ/kxitYKReF8r6pXgzZJ5VaB4t64onZqmrLh+gfDrCFjdrsM03
WuMBLjroayjFcHQ9QRJqullVHj7L+yRFQWDXcVE0AmnR+DpSPkfTIUuXU3u5lXFR
d896iX/SDrGTK1IG5oj/OeaCkb3MmTVjvCK0QUNNMer/2QYYQy+dN82W+H+96NLb
kbTXg48q9ZwbbPY8O9Wau8JpIA5zIjLLOsMKtzAFr8K9N6pVInpclXS/Vdcvultn
lE2x0mUVhVpRvmfTK5g6Y/DUliPU2pgB0fr7UiiCnCXteWXUe+A=
=udUK
-----END PGP SIGNATURE-----
Bug fix releases are done "on demand" and there is no strict policy to
not do a bug fix release for older versions.
However, in practice bug fix release for older versions don't happen
very often. The release plan wiki page gives a good overview about
release in the past:
https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
(Or check out the download page to get all release dates:
https://kafka.apache.org/downloads)
Thus, 2.1 might get a new bug-fix release in the future, independent of
the 2.4 release. However, it's very unlikely.
Hope that helps.
-Matthias
On 10/30/19 3:23 AM, Vitalii Stoianov wrote:
> Hi All,
>
> I'm trying to understand Kafka EOL policy. As stated in
> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> *"""*
>
>
>
>
> *What Is Our EOL Policy?Given 3 releases a year and the fact that no one
> upgrades three times a year, we propose making sure (by testing!) that
> rolling upgrade can be done from each release in the past year (i.e. last 3
> releases) to the latest version.We will also attempt, as a community to do
> bugfix releases as needed for the last 3 releases.*
> *"""*
>
> So does it mean that 2.1.0 is latest release that is supporting any
> bugfixing as for now and when 2.4 will be released 2.1.0 won't get any
> further bugfixes?
> if not please help me to understand which one is supporting bugfixing as
> for now and when it will lose support.
> Any help is appreciated.
>
> Regards,
> Vitalii.
>
Comment: GPGTools - https://gpgtools.org
iQIzBAEBCgAdFiEE8osu2CcCCF5douGQu8PBaGu5w1EFAl26p+EACgkQu8PBaGu5
w1Fy+w//aS5d6PYmALndO9fnd2FfSrQXI12ZylEgli2SWZYkwnxeza+dNWAS0tkF
iG2xWVZ7DCLzdkvzwn9YUyBZ2DXDP6KOaLjWjxbKdLqggWxV/faaihUcnMtcrIDO
YkEe/k0GRDW0QuIW43pckdFJb8/dYyxEnB8xeWTzMOm2w4Cq6/wEKkgVI7HJDPCT
teXV+URjEqE/S0erxwUspy78p22st6n/oMUxQKTWQEcynmWOEiDwB2/szMVIn5EN
OJIN/lgg3EM+sUlfNRP6JyW+2fwvViWWMvJ5RhHBWDtaYnuJtUeE1hM6VUnR3kt2
yhYzwjtO8EKJN4LOPJpiSW+y0TFQMPL9o1kVd6jaX7PGNAU7fAOr8asxhZQ0iEA/
W16+fKPh17vw2kZ/kxitYKReF8r6pXgzZJ5VaB4t64onZqmrLh+gfDrCFjdrsM03
WuMBLjroayjFcHQ9QRJqullVHj7L+yRFQWDXcVE0AmnR+DpSPkfTIUuXU3u5lXFR
d896iX/SDrGTK1IG5oj/OeaCkb3MmTVjvCK0QUNNMer/2QYYQy+dN82W+H+96NLb
kbTXg48q9ZwbbPY8O9Wau8JpIA5zIjLLOsMKtzAFr8K9N6pVInpclXS/Vdcvultn
lE2x0mUVhVpRvmfTK5g6Y/DUliPU2pgB0fr7UiiCnCXteWXUe+A=
=udUK
-----END PGP SIGNATURE-----
Bug fix releases are done "on demand" and there is no strict policy to
not do a bug fix release for older versions.
However, in practice bug fix release for older versions don't happen
very often. The release plan wiki page gives a good overview about
release in the past:
https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
(Or check out the download page to get all release dates:
https://kafka.apache.org/downloads)
Thus, 2.1 might get a new bug-fix release in the future, independent of
the 2.4 release. However, it's very unlikely.
Hope that helps.
-Matthias
On 10/30/19 3:23 AM, Vitalii Stoianov wrote:
> Hi All,
>
> I'm trying to understand Kafka EOL policy. As stated in
> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> *"""*
>
>
>
>
> *What Is Our EOL Policy?Given 3 releases a year and the fact that no one
> upgrades three times a year, we propose making sure (by testing!) that
> rolling upgrade can be done from each release in the past year (i.e. last 3
> releases) to the latest version.We will also attempt, as a community to do
> bugfix releases as needed for the last 3 releases.*
> *"""*
>
> So does it mean that 2.1.0 is latest release that is supporting any
> bugfixing as for now and when 2.4 will be released 2.1.0 won't get any
> further bugfixes?
> if not please help me to understand which one is supporting bugfixing as
> for now and when it will lose support.
> Any help is appreciated.
>
> Regards,
> Vitalii.
>
Comments
Post a Comment