So, how long will there be AG iOS 1.5 without any available support for AG Push
Registration?

It would make sense to me to stage&test 1.5 now and then wait for AG Push
Registration 0.9.0 to happen, stage&test. Then push both into the wild
simultaneously.

Karel

On Tue, 18 Mar 2014 11:09:34 +0100
Corinne Krych <corinnekrych@gmail.com> wrote:

> +1
> Here's the plan.
> Back to testing.
> ++
> Corinne
> On 18 Mar 2014, at 11:07, Matthias Wessendorf <matzew@apache.org> wrote:
>
> >
> >
> >
> > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych <corinnekrych@gmail.com>
> > wrote: Yep indeed coordination is needed, let’s see how we progress on
> > removing AFNetworking dep. When releasing 1.5 we’ll go either:
> > 0.8.2 => with AFNetworking 2.2.1
> >
> > sounds like an odd thing, due to item below
> >
> >
> > or 0.9.0 => without AFNetworking dep
> >
> > +1
> >
> >
> > Keep you posted (very soon) on that.
> >
> > ++
> > Corinne
> > On 18 Mar 2014, at 10:47, Sebastien Blanc <scm.blanc@gmail.com> wrote:
> >
> > > But until AG Push registration 0.9 is released , 0.8.1 do not work with
> > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it make
> > > sense to make a 0.8.2 release with an updated pod (what Corinne
> > > mentionned in the second message) to "fill the gap" until 0.9 is
> > > released ?
> > >
> > >
> > >
> > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf <matzew@apache.org>
> > > wrote:
> > >
> > >
> > >
> > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych <corinnekrych@gmail.com>
> > > wrote: True, eventually we will remove that dependency.
> > > What about getting 1.5 out of the way and then release AG Push
> > > registration 0.9.0 without AFNetworkin dependency?
> > >
> > >
> > > sounds good to me!
> > >
> > >
> > > ++
> > > Corinne
> > > On 18 Mar 2014, at 09:53, Matthias Wessendorf <matzew@apache.org> wrote:
> > >
> > > > Corinne,
> > > >
> > > > no AFN on that project, in the future:
> > > > https://issues.jboss.org/browse/AGPUSH-558
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych <corinnekrych@gmail.com>
> > > > wrote: Hello Sebi
> > > >
> > > > Actually PR are on their ways (as we test it) to set proper version,
> > > > what you need here
> > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile
> > > > is to upgrade to: platform :ios, ‘7.0'
> > > > pod 'AFNetworking', ‘2.2.1'
> > > >
> > > > Note that we’ll support from ios 7.0
> > > > Feel free to send the PR with Podfile update if the testing works for
> > > > you.
> > > >
> > > > ++
> > > > Thanks for the feedback,
> > > > Corinne
> > > >
> > > > On 18 Mar 2014, at 09:44, Sebastien Blanc <scm.blanc@gmail.com> wrote:
> > > >
> > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`-
> > > > > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`-
> > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`-
> > > > > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`-
> > > > > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`-
> > > > > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`-
> > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`-
> > > > > `AFNetworking/Serialization` required by
> > > > > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability`
> > > > > required by `AFNetworking/NSURLConnection (2.2.1)`-
> > > > > `AFNetworking/Security` required by `AFNetworking/NSURLConnection
> > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by
> > > > > `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection`
> > > > > required by `AFNetworking/UIKit (2.2.1)
> > > >
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev@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
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev@lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev@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
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev@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
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev