Re: [aerogear-dev] house keeping on demo repos

Hello guys As suggested by @passos and @abstractj I’ve just moved AeroDoc demo into our cookbook [1], [2] leaving old repo empty and deprecated. For iOS we have 2 branches of our cookbook 1.6.X for objc support with 1.X AeroGear and master (swift 2.X libs). Some demos like AeroDoc will go to 1.6.x as our 2.X Swift libs are not features complete (we’re missing storage implementation for now). Demos that implements features supported by 2.x will go on cookbook master. On Android/Js/Windows side do you have plan (ie: JIRA tickets) to move : - otp demo: https://github.com/aerogear/aerogear-otp-ios-demo - crypto demo: https://github.com/aerogear/aerogear-crypto-ios-demo - push demo: https://github.com/aerogear/aerogear-push-ios-demo - helloworld - push quickstart contacts - sync jedi demo (for iOS we already have a ticket for that [3]) I’d like to make sure we’re going in the same direction and create the missing tickets.

Thanks for your feedback ++ Corinne [1] https://issues.jboss.org/browse/AGIOS-378 [2] https://github.com/aerogear/aerogear-ios-cookbook/pull/61 [3] https://issues.jboss.org/browse/AGIOS-337 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev