Hello,
as mentioned in [1] we should have a code-freeze period of a few days before we do the final release.
Release for UPS.1.0.0.Final date will be August 26th.
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
'blocker' or 'critical' fixes should be allowed to be merged during that time (to that particular branch/tag).
Basic goal: minimize risks!
(The JIRA tickets for the umbrella "Mobile Push 1.0" are almost all around Quickstarts and our docs, see [2])
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]).
The version number on the "1.0.x" branch will start with 1.0.1-SNAPSHOT
On MASTER branch, I'd like to set the version to 1.1.0-SNAPSHOT.
Fixes done on the 1.0.x branch will be merged/cherry-picked MASTER branch as well.
Moving forward to our next 1.1.0 UPS release, on MASTER, we will be working on new features, like:
* More analytics
* More mobile network (Windows, Kindle, etc)
* JavaEE7 updates (focus on WildFly / Undertow, ConcurrencyUtils, etc)
* Alternative Datastores (like Mongo) ?
Any thoughts ?
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf