<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">sounds good Matthias<div><div><div><br></div><div>-</div><div>Christos</div><div><br><div><div>On Aug 18, 2014, at 4:11 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>Hello,<br></div><div><br></div><div>as mentioned in [1] we should have a code-freeze period of a few days before we do the final release.</div><div>Release for UPS.1.0.0.Final date will be August 26th.</div>
<div><br></div><div>I'd like to do the code-freeze tomorrow(Tuesday, 19th) evening. I'd like to create a 1.0.0.Final tag (or a branch) and only</div><div>'blocker' or 'critical' fixes should be allowed to be merged during that time (to that particular branch/tag).</div>
<div>Basic goal: minimize risks!</div><div><br></div><div>(The JIRA tickets for the umbrella "Mobile Push 1.0" are almost all around Quickstarts and our docs, see [2])</div><div><br></div><div><br></div><div>Once the 1.0.0.Final is released, I'd like to create a 1.0.x branch for follow-up releases, as needed (see [3]).</div>
<div>The version number on the "1.0.x" branch will start with 1.0.1-SNAPSHOT</div><div>On MASTER branch, I'd like to set the version to 1.1.0-SNAPSHOT.</div><div><br></div><div>Fixes done on the 1.0.x branch will be merged/cherry-picked MASTER branch as well.</div>
<div><br></div><div><br></div><div>Moving forward to our next 1.1.0 UPS release, on MASTER, we will be working on new features, like:</div><div>* More analytics</div><div>* More mobile network (Windows, Kindle, etc)</div>
<div>* JavaEE7 updates (focus on WildFly / Undertow, ConcurrencyUtils, etc)</div><div>* Alternative Datastores (like Mongo) ? </div><div><br></div><div><br></div><div>Any thoughts ?</div><div>-Matthias</div><div><br></div>
<div><br></div><div>[1] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html">http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html</a> </div><div>[2] <a href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel">https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel</a></div>
<div>[3] <a href="http://aerogear.org/docs/planning/roadmaps/UnifiedPush/">http://aerogear.org/docs/planning/roadmaps/UnifiedPush/</a></div><div><br></div><div><br></div>-- <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>
</div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></div></div></div></body></html>