+1On Thu, Feb 25, 2016 at 8:05 AM Stian Thorgersen <sthorger@redhat.com> wrote:What I'm going to do is:* Short term - start mentioning important migration issues in release announcement and link to migration doc* Long term - start creating proper release notes and include in documentation, release announcement in the future will just be highlights and link to thisComments?On 25 February 2016 at 11:36, Edgar Vonk - Info.nl <Edgar@info.nl> wrote:that would certainly help indeed!
as an example this is how Magnolia (a Java CMS we often use in our projects) does it:
I think they removed it now but they even had a automatically generated section in their release notes with a list of people who ‘contributed’ by reporting issues in JIRA that were fixed in the release. A way to attach your users to your product I guess.
On 25 Feb 2016, at 11:24, Marek Posolda <mposolda@redhat.com> wrote:
Maybe the best chance people won't miss it, is to put the note into release announcement? Just something high level like "We changed location of themes and did some other changes XYZ. Don't forget to read migration guide for more details" or something like that?
Marek
On 25/02/16 10:28, Stian Thorgersen wrote:
Bruno: No need to update theme chapter - Marc from APIMan is already on the task :)
"Before you get started" will that be read though? I can't see current users reading that.
On 25 February 2016 at 10:25, Bruno Oliveira <bruno@abstractj.org> wrote:
I will review the whole theme chapter today and see if I find any mismatches.
Regarding your question, I'd add a section in the very beginning of our guide called "Before you get started".
On Thu, Feb 25, 2016 at 6:23 AM Stian Thorgersen <sthorger@redhat.com> wrote:
Any tips on how we can make it more obvious to users to read the migration guide?_______________________________________________
On 25 February 2016 at 10:21, Edgar Vonk - Info.nl <Edgar@info.nl> wrote:
ok, thanks! you are right, I should have read the migration guide.
On 25 Feb 2016, at 10:19, Stian Thorgersen <sthorger@redhat.com> wrote:
Yes, it has moved. I forgot to update the themes doc, but it's included in the migration guide.
Always read the migration guide before upgrading! It will quite likely save you a lot of time.
On 25 February 2016 at 10:00, Thomas Darimont <thomas.darimont@googlemail.com> wrote:
This was discussed a few days ago on the dev list:
Perhaphs there should have sent a mail to the user-list as well...
Cheers,Thomas
2016-02-25 9:31 GMT+01:00 Edgar Vonk - Info.nl <Edgar@info.nl>:
Hi,
It seems that the themes folder has moved in Keycloak 1.9.0.Final (from 1.9.0.RC1)?
The themes folder used to be:
$KEYCLOAK_HOME/standalone/configuration/themes
but now it seems to be:
$KEYCLOAK_HOME/themes
The documentation still mentions the old location so I think needs to be updated?
http://keycloak.github.io/docs/userguide/keycloak-server/html/themes.html#d4e2431
cheers
Edgar
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user