[aerogear-dev] [RFC] future Roadmap for Unified Push Server

Matthias Wessendorf matzew at apache.org
Tue Jul 7 17:51:35 EDT 2015

Hi team,

as we are moving forward w/ the releases, and we are close to have our
1.1.0.Final, I started to think about a proposal for a near-term future
roadmap, and I'd like to get feedback, comments (or tomatos) on it.
1.1.x (July/August)

   - 1.1.0 -> very soon
   - 1.1.x -> perhaps some needed bug fixes/improvements, in a short
   interval :-)

1.2.0 (September/October)

We have a release version
<https://issues.jboss.org/browse/AGPUSH/fixforversion/12327301> in JIRA

*Key features*

   - Keycloak isolation
   - GCM 3 support (client and server)
   - Improved docker support (e.g. tests/test suite -> Hopefully Travis
   supports 'docker run' by than ;-))

One could think that going back to JPA annotations is a key feature as well
1.2.x (or even 1.3.0) (December 2015)

There is no concrete release version for this, but we have a larger
ups-future <https://issues.jboss.org/browse/AGPUSH/fixforversion/12321884>
in JIRA. The ups-future version/label has a few interesting things, that we
may have to do right after 1.2.0

*Key features*

   - APNs goes HTTP2 (a must)
   - Quiete time for push (aka timezone awareness of devices)
   - Scheduled pushes
   - Proxy server support

2.0.0 (March-2016)

In October (2015) the WildFly 10
<http://lists.jboss.org/pipermail/wildfly-dev/2015-June/004129.html> should
be released and I'd like to see us adapting this for the 2.0.0 series! Also
for a possible release of our 2.0.0 in March 2016, I’d like to stop the 1.x

*Note:* We don't have a release version for JIRA here, but heck! this mail
is asking for feedback ;-)

*Key features / Core changes*

   - UPS based on (public) APIs that are available in WildFly-10
      - looking at using WF feature packs
      <https://developer.jboss.org/wiki/WildflyProvisioning> (similar to
      what Keycloak did, e.g. for layered "product"
      - looking at getting an UPS sub-system
   - Java8 only (as well as making sure works w/ Java9)
   - internal communication fully based on messaging (A-MQ / HornetQ)
   - WildFly-Swarm launcher (aka fat JARs)
      - helps with a more modular system:
   - Modular system (e.g. different “webapps”, like "sender.war",
   "registration.war", "UI WAR" etc)
      - allows us to play with different platforms for the different “web
      - e.g. for a 2.x.y we could see/experiment how a vertx microservice
      (e.g. for the device registration) will behave in the larger system

Other new features, e.g. based on needs and/or requests could be weaved
into 2.0.0 or 2.0.x, based on timing.

Please review this initial draft of a roadmap - once we are all in
agreement, it's time to hammer the roadmap into stone, uhm... JIRA :-)


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/20150707/103afe65/attachment-0001.html 

More information about the aerogear-dev mailing list