[aerogear-dev] [UnifiedPush Server] release timelines

Hi team, based on [1] I thought about our release timelines until 1.0.0.Final, and shortly after. - 1.0.0.Beta2 <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325092/?selectedTa...;: 07/Aug/14 This needs to include Keycloak-beta4, and might slip by one day, but not much more of a delay. *Please note:* There is already works going on to have our parent and UPS working w/ beta4 - it’s just a matter of merging the branch, once the release is out. Number of open JIRAs for this release is looking good! - 1.0.0 <https://issues.jboss.org/browse/AGPUSH/fixforversion/12323754/?selectedTa...;: 18/Aug/14 *Keycloak:* This will use keycloak’s beta4 as well, unless we find BLOCKERS in their beta4... (As said before KC is mostly hidden inside the server, and we can not wait for their 1.0.0.Final in September) This release will be mostly around docs and perhaps some more UX review of the quickstart demos. It is possible that the UX review does not happen. *CODE FREEZE:* I’d suggest we do a *code freeze* for the UnifiedPush Server on 11/Aug/14. This is pretty much shortly after the beta2 and gives us one week of deep testing (of server, docs, demos) before the final release. Next: *celebrate*!!!!!!!! [image: :tada:] After the 1.0.0.Final of UPS, I’d suggest a two week-based release series of small fixes and improvements, as well as taking up new Keycloak releases - 1.0.1 <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325080/?selectedTa...;: 01/Sep/14 *Keycloak:* main reason is pick-up of their 1.0-RC-1 and those few items from the JIRA. - 1.0.2 <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325081/?selectedTa...;: 15/Sep/14 *Keycloak:* main reason is pick-up of their 1.0.0.Final - 1.0.3 <https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082/?selectedTa... :29/Sep/14 Might not be needed - but added it to JIRA, just in case… Let me know your thoughts and I will update the roadmap! -Matthias [1] http://lists.jboss.org/pipermail/keycloak-dev/2014-July/002360.html -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf