Last Tuesday during our (favourite) iOS meeting   we talked about modularization. We agreed with Android team modularization is scheduled for 2.0.
For iOS we have several actions:
1. rename existing repos (too bad we don’t follow well Android convention)
• aerogear-ios-push (thanks passos for the suggestion)
Since we’re talking about renaming, what about dropping “arerogear” for the repo name? all those repos belong to aerogear organization anyway. Maybe removing the aerogear part will stress more the small libraries aspect. Maybe sth we already discussed but can’t remember/find it. wdyt?
2. Pipe and Store deprecated. All aerogear-ios we’ll stick to 1.7 version and will be marked deprecated.
But …. don’t be scared new modules will replace them:
• aerogear-ios-http : Lightweight lib around NSURLSession to ease HTTP calls with pluggable request and response Serializers. Very very Draft version  with some cookbook recipe . With this module we will work directly with NSURLSession (iOS foundation networking) instead of using AFNetworking. Sure Andrea will like it: no dependency :)
• aerogear-ios-oauth2 : dependent on aerogear-ios-http, bring all the good stuff like AccountManager, OAuth2 extensible adapters, fluid http post/get ...
• aerogear-ios-storage usage of incrementalStorage to plug into Core Data
Those modules will be written in Swift code. We’ll test them both in iOS7 and iOS8.
3. Cookbook recipes rpo
• tag our repo 1.7: we didn’t have a tag strategy for cookbook demos but with the move from 1.X to 2.) I think we should
* Swift demo naming convention add “-swift” for Swift version like we did . We should also append “-objc” to other recipes to be consistent.
4. Differentiate Swift vs Objective-C libs
How to differenctiate Swift code. Specially for aerogear-ios-push which will be declined in 2 versions? One suggestion from Matthias was to have 2 separate branches.
master -> objc-c
until iOS8 is released and stable.
I’m +1 with that idea.
Let me know if you have suggestions/objections. When we reach an agreement, I’ll create associated JIRA.
After taking a look at the PR  that Matthias made on AeroGear JS, I have
noticed that some of our library's dependencies have been changed. For
integration tests is 2.0.0.Final. However the new version is 2.1.2. The
been changed since Jan 29 so the AeroGear-JS notifier adapter needs to
comply with these changes.
I would suggest to lock the dependency versions and update our docs to
point these specific versions (at least for the cases where the
dependencies API is changed and AeroGear-JS code needs to be updated). Then
we can open JIRA(S) and start updating the code.
1.0.0.Beta2 is out and 1.0.0.Final is around the corner!
The list of open JIRAs is looking really good (see ). The most tickets
are around our quickstart demos and documentation. There are a few tickets
that require commits to the UPS itself. Gabriel did a review of the UX/UI
and filed three tickets (AGPUSH-934, AGPUSH-935 and AGPUSH-936) that he and
Lukas will be working on.
The release date for the 1.0.0.Final will be August 25th/26th and therefore
I propose to do a 'code freeze' for the UPS around the 19th or 20th August
to ensure its stability. However, in case something comes up (e.g. during
testing), I think only 'blocker' or 'critical' fixes should be allowed to
be merged during that time. Goal is to minimize risks!
Once the UPS 1.0.0.Final is out, there are a few 1.0.x release planed to
address things (if needed) and picking up new releases of our own
dependencies (e.g. Keycloak)
Any thoughts ?
After successful testing I’m happy to announce that the 0.7.0 version of the aerogear-pushplugin has been released. Thanks to everyone involved in making this release happen.
The new features bugs fixed are:
[AGCORDOVA-22] - android binaries installed for other platforms
[AGCORDOVA-23] - Support content title with gcm notifications on android
[AGCORDOVA-25] - iOS8 support for push registration