[aerogear-dev] UnifiedPush Server: Code-Freeze - and UPS.next

[Matthias Wessendorf]

Hi Summers!

Thanks for your feedback, some comments inline


On Mon, Aug 18, 2014 at 10:57 PM, Summers Pittman <supittma at redhat.com>
wrote:

>  On 08/18/2014 09:11 AM, Matthias Wessendorf wrote:
>
>  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
>
> +1 in principle, which are you thinking of?
>

e.g. app opened, app opened due to push. like we discussed at the Face2Face:
http://oksoclap.com/p/jbrS1EHWkI

Some of the "UPS.next" items are already captured in JIRA, some not. Once
the 1.0.0.Final is out, I will have more time to create more JIRAs for 1.1.x


>
>  * More mobile network (Windows, Kindle, etc)
>
> +1
>
>  * JavaEE7 updates (focus on WildFly / Undertow, ConcurrencyUtils, etc)
>
> Can you be more specific?  What problems/shortcomings are we trying to
> solve?
>
As discussed in the above oksoclap, this might be lower priority. Nothing
specific planed here, besides updating to the latest specs, if needed. For
instance the concurrency utils from EE7 could be an option for us to get
rid of async.

>
>  * Alternative Datastores (like Mongo) ?
>
> What do we get from Mongo other than to say "we support mongo"?
>

yeah, I am not sure here too :-) Mongo was a request from the mailing list
early 2014. At face2face, in a phone call, Emmanuel suggested Hibernate
OGM, so this *might* be something we do, or not.


Currently we have these JIRAs for 1.1.x:
https://issues.jboss.org/browse/AGPUSH/fixforversion/12323762/

and based on the clap, some more will follow, but that happens once the
1.0.0 is out :-)

Greetings,
Matthias


>
>
>  Any thoughts ?
> -Matthias
>
>
>  [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-August/008810.html
>
> [2]
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
> [3] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140819/b79effd2/attachment.html