Agreed - we need to run the old CI setup before every release (Beta and
On 7 February 2018 at 10:53, Hynek Mlnarik <hmlnarik(a)redhat.com> wrote:
Then until we are able to check DBs at PR level, we should run at
start Keycloak on all supported DBs before promoting Beta release to make
sure the changelogs are sane - to prevent issues like [1, 2]
On Wed, Feb 7, 2018 at 8:44 AM, Stian Thorgersen <sthorger(a)redhat.com>
> We would need to support migration between beta releases.
> On 6 February 2018 at 21:01, Hynek Mlnarik <hmlnarik(a)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
>> On Tue, Feb 6, 2018 at 8:22 PM, Stian Thorgersen <sthorger(a)redhat.com>
>>> As we've started working in 3 week sprints we are considering a new
>>> model for Keycloak.
>>> What we are considering is doing a Beta release for every sprint, then
>>> every 4th sprint (each quarter) we plan to do a Final release.
>>> For a beta release existing features will be considered stable, while
>>> features may not be ready for prime time. The recommendation will still
>>> 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
>>> a Final release is available.
>>> keycloak-dev mailing list