<div dir="ltr">+1 for consistency and release dates. But I'd keep the release version independent, move from 0.0.16 to 1.9.2 for example, is a huge bump.</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Apr 11, 2016 at 1:43 PM Stian Thorgersen <<a href="mailto:sthorger@redhat.com">sthorger@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">We discussed this at the f2f and I believe we should keep it consistent across all adapters.</p>
<p dir="ltr">The decision was to have all adapters released when the server is released and they will have the same version numbers. We will also make sure release notes mark which adapters have changed and also which are required to update (either due to compatibility changes or security related fixes).</p>
<p dir="ltr">So I'd like the ability to release nodejs adapters at the same time I do the release of the server.</p>
<p dir="ltr">We can certainly discuss changes to the above, but it should be consistent for all our adapters.</p>
<div class="gmail_quote"></div><div class="gmail_quote">On 11 Apr 2016 17:09, "Bruno Oliveira" <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>> wrote:<br type="attribution"></div><div class="gmail_quote"><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal">Good morning, </span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><br style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal">Today I was chatting with Lance about the release cadence for Node.js adapters. </span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><br style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal">My initial idea was to release the adapters at exactly the same release dates as the official Keycloak release in order to guarantee compatibility. For critical/urgent patches, we just release those modules based on our judgment.</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><br style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal">Lance would like more flexibility between those releases. For example, release npm modules before the official release for situations where a user wants </span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal">some new capability that is perhaps unrelated to changes in KC itself e.g. a move to promises.</span><div style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;line-height:normal">I don't have any problems on keeping Node.js adapters' release independent from official KC release, but would like to hear more opinions about it.<font color="#888888"><br><br>-- <br><br><br>-<br>abstractj</font></div></div>
<br></blockquote></div><div class="gmail_quote"><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></blockquote></div>
</blockquote></div>