<div dir="ltr"><div>Hi folks,<br></div><div><br></div><div>for early Jan, I'd like to get the UPS-1.1.1 out:</div><div><a href="https://issues.jboss.org/projects/AGPUSH/versions/12327457">https://issues.jboss.org/projects/AGPUSH/versions/12327457</a></div><div><br></div><div>Not sure we will be doing a 1.1.2 later, but maybe... given these JIRAs:</div><div><a href="https://issues.jboss.org/projects/AGPUSH/versions/12323762">https://issues.jboss.org/projects/AGPUSH/versions/12323762</a></div><div><br></div><div>The next minor version will be 1.2.0:</div><div><a href="https://issues.jboss.org/projects/AGPUSH/versions/12327301">https://issues.jboss.org/projects/AGPUSH/versions/12327301</a></div><div><br></div><div>However, I had quick chat w/ Lukas in the morning, that we already have KC version update on master, but that really should not be in a 1.1.x patch version.</div><div><br></div><div>Here is the proposal of what to do:</div><div>* I branch of master for a 1.1.x patch branch, and on that branch, I simply rewert the KC update.</div><div>* Obviously on master we keep the update, but also update the version there to 1.2.0-SNAPSHOT</div><div><br></div><div>Also, since "active" branches are a PITA (we had that on 1.0.x), the idea is that the 1.1.x branch will be deleted ASAP, e.g. once we get out 1.1.1 shipped. In case we do a 1.1.2, we'd simple create a new 1.1.x branch of the 1.1.1 TAG.</div><div><br></div><div>But on master, things will be moving forward, towards UPS 1.2.0</div><div><br></div><div><br></div><div>Any thoughts?</div><div><br></div><div><br></div><div>-Matthias</div><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div>