[keycloak-dev] Updated release cadence

[Stian Thorgersen]

Adding something around fixes.

A final release would not receive any backported bug fixes. For those that
want supported versions there is RH-SSO.

We should however do backporting of critical security issues. We would only
backport security fixes to the current Final release.

So we could have the following releases:

* 4.0.0.Beta1/2/3
* 4.0.0.Final
* 4.1.0.Beta1/2/3
* 4.1.0.Final
* 4.2.0.Beta1
* 4.1.1.Final (to include a single critical security vulnerability, note
there would be no 4.0.1.Final)

On 7 February 2018 at 11:26, Stian Thorgersen <sthorger at redhat.com> wrote:

> Agreed - we need to run the old CI setup before every release (Beta and
> Final)
>
> On 7 February 2018 at 10:53, Hynek Mlnarik <hmlnarik at redhat.com> wrote:
>
>> Then until we are able to check DBs at PR level, we should run at least
>> start Keycloak on all supported DBs before promoting Beta release to make
>> sure the changelogs are sane - to prevent issues like [1, 2]
>>
>> [1] https://issues.jboss.org/browse/KEYCLOAK-5235
>> [2] https://issues.jboss.org/browse/KEYCLOAK-5416
>>
>> On Wed, Feb 7, 2018 at 8:44 AM, Stian Thorgersen <sthorger at redhat.com>
>> wrote:
>>
>>> We would need to support migration between beta releases.
>>>
>>> On 6 February 2018 at 21:01, Hynek Mlnarik <hmlnarik at redhat.com> wrote:
>>>
>>>> Until now we have only supported database migration from Final to
>>>> Final, i.e. not from CR1 to .Final. So when a change happened in between
>>>> CR1 and Final, we did not care. What will be the supported path now? Will
>>>> we support migrating from Beta1 to Beta2 to Beta3 to Final or only from
>>>> Final to Final? I'd rather the latter but it seems we'll have to support
>>>> the former.
>>>>
>>>> On Tue, Feb 6, 2018 at 8:22 PM, Stian Thorgersen <sthorger at redhat.com>
>>>> wrote:
>>>>
>>>>> As we've started working in 3 week sprints we are considering a new
>>>>> release
>>>>> model for Keycloak.
>>>>>
>>>>> What we are considering is doing a Beta release for every sprint, then
>>>>> for
>>>>> every 4th sprint (each quarter) we plan to do a Final release.
>>>>>
>>>>> For a beta release existing features will be considered stable, while
>>>>> new
>>>>> features may not be ready for prime time. The recommendation will
>>>>> still be
>>>>> to upgrade to always update to the latest release to receive the latest
>>>>> security fixes and other fixes.
>>>>>
>>>>> However, care should be taken before using new features in production
>>>>> until
>>>>> a Final release is available.
>>>>>
>>>>> Thoughts?
>>>>> _______________________________________________
>>>>> keycloak-dev mailing list
>>>>> keycloak-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> --Hynek
>>>>
>>>
>>>
>>
>>
>> --
>>
>> --Hynek
>>
>
>