<div dir="ltr">+1 Sounds good to me getting RC1 in.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 20 August 2014 23:12, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 on get RC1 in.<br>
<div><div class="h5"><br>
On 2014-08-20, Matthias Wessendorf wrote:<br>
> Hello,<br>
><br>
> I will tag tomorrow morning.<br>
> This PR will get in as well<br>
> <a href="https://github.com/aerogear/aerogear-unifiedpush-server/pull/364" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server/pull/364</a><br>
><br>
> This gives us a few days (Thurs, Friday, Monday, Tuesday, and perhaps<br>
> Wednesday next week) to test the TAG.<br>
> So we can have the release to Maven Central by next Wednesday/Thursday.<br>
><br>
> Oh, one more thing:<br>
> ATM Bill Burk is already doing the rc-1 release, followed by a rc-2 next<br>
> week:<br>
> <a href="http://lists.jboss.org/pipermail/keycloak-dev/2014-August/002460.html" target="_blank">http://lists.jboss.org/pipermail/keycloak-dev/2014-August/002460.html</a><br>
><br>
> If there are no concerns, I'd like to get that rc-1 in as well. It fixes a<br>
> few minor bugs on our "UI":<br>
> * <a href="https://issues.jboss.org/browse/AGPUSH-950" target="_blank">https://issues.jboss.org/browse/AGPUSH-950</a> -> Luke found it<br>
> * logout sessions from KC admin, works not 100% w/ beta4. noticed tonight.<br>
> Tested w/ rc-1 -> works there.<br>
><br>
><br>
> Any thoughts?<br>
><br>
> Thanks!<br>
> Matthias<br>
><br>
><br>
><br>
> On Mon, Aug 18, 2014 at 3:11 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>><br>
> wrote:<br>
><br>
> > Hello,<br>
> ><br>
> > as mentioned in [1] we should have a code-freeze period of a few days<br>
> > before we do the final release.<br>
> > Release for UPS.1.0.0.Final date will be August 26th.<br>
> ><br>
> > I'd like to do the code-freeze tomorrow(Tuesday, 19th) evening. I'd like<br>
> > to create a 1.0.0.Final tag (or a branch) and only<br>
> > 'blocker' or 'critical' fixes should be allowed to be merged during that<br>
> > time (to that particular branch/tag).<br>
> > Basic goal: minimize risks!<br>
> ><br>
> > (The JIRA tickets for the umbrella "Mobile Push 1.0" are almost all around<br>
> > Quickstarts and our docs, see [2])<br>
> ><br>
> ><br>
> > Once the 1.0.0.Final is released, I'd like to create a 1.0.x branch for<br>
> > follow-up releases, as needed (see [3]).<br>
> > The version number on the "1.0.x" branch will start with 1.0.1-SNAPSHOT<br>
> > On MASTER branch, I'd like to set the version to 1.1.0-SNAPSHOT.<br>
> ><br>
> > Fixes done on the 1.0.x branch will be merged/cherry-picked MASTER branch<br>
> > as well.<br>
> ><br>
> ><br>
> > Moving forward to our next 1.1.0 UPS release, on MASTER, we will be<br>
> > working on new features, like:<br>
> > * More analytics<br>
> > * More mobile network (Windows, Kindle, etc)<br>
> > * JavaEE7 updates (focus on WildFly / Undertow, ConcurrencyUtils, etc)<br>
> > * Alternative Datastores (like Mongo) ?<br>
> ><br>
> ><br>
> > Any thoughts ?<br>
> > -Matthias<br>
> ><br>
> ><br>
> > [1] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html</a><br>
> > [2]<br>
> > <a href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel" target="_blank">https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel</a><br>
> > [3] <a href="http://aerogear.org/docs/planning/roadmaps/UnifiedPush/" target="_blank">http://aerogear.org/docs/planning/roadmaps/UnifiedPush/</a><br>
> ><br>
> ><br>
> > --<br>
> > 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><br>
> ><br>
><br>
><br>
><br>
> --<br>
> 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><br>
<br>
</div></div><div class="">> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
--<br>
<br>
</div>abstractj<br>
PGP: 0x84DC9914<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>