> On Jun 8, 2022, at 11:44 AM, Matteo Merli <matteo.me...@gmail.com> wrote:
>
> On Tue, Jun 7, 2022 at 10:14 PM PengHui Li <peng...@apache.org> wrote:
>>
>> I'm not sure I fully understand the LTS release and feature release.
>>
>>> The LTS releases will be identified by being a `.0` version. For example:
>>> * `3.0` -> LTS
>>> * `3.1` -> regular release
>>> * `3.2` -> regular release
>>> * `4.0` -> LTS
>>
>> In this example, we can only introduce new features in 3.1 and 3.2,
>> and 3.1.x and 3.2.x should be the patch release based on the feature
>> release?
>
> Exactly, that aspect won't be changed. I will clarify more in the document.
>
>> We can have one patch release for a month.
>>
>> 3.0.x is the LTS release that will support at most three years.
>> After we have 4.0 LTS release, we will still support 3.0.x TLS for at least
>> 18 months.
>> And 4.0 TLS will have all the new features from 3.x
>
> Correct.
>
>
>>> This can be translated into:
>>> * We support the last 2 LTS releases and the last 2 feature releases
>>> * Security patches are provided for the past 3 LTS releases and 2
>>> feature releases
>>
>> Does this mean we can introduce new features in 3.x even if we have 4.x?
>> And how many patch releases for the feature releases we will support,
>> such as 3.1.x, 3.2.x, 3.3.x, 4.1.x, 4.2.x.
>>
>> I think 2 feature releases means 3.x and 4.x here?
>
> At the moment when 4.0.0 is released, there won't be any new feature
> release in 3.x.
>
> Based on the 18months schedules we would have 1 LTS followed by 5
> non-LTS releases (without counting patch releases). There won't be any
> 3.x feature release after 3.5.
>
> Example using hypothetical dates:
> * Jan 2023 --- 3.0
> * Apr 2023 --- 3.1
> * Jul 2023 --- 3.2
> * Oct 2023 --- 3.3
> * Jan 2024 --- 3.4
> * Apr 2024 --- 3.5
> * Jul 2024 --- 4.0
> * Oct 2024 --- 4.1
> * ….
Schedules always slip. Would you say that if the 3.x feature releases take too
long with these hypothetical dates that 3.5 would be dropped in order to
release 4.0 on schedule?
ATB,
Dave
