Re: [keycloak-dev] Updated release cadence
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
--Hynek