<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yep indeed coordination is needed, let’s see how we progress on removing AFNetworking dep.<br>
When releasing 1.5 we’ll go either:<br>
0.8.2 => with AFNetworking 2.2.1<br></blockquote><div><br></div><div>sounds like an odd thing, due to item below</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
or 0.9.0 => without AFNetworking dep<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Keep you posted (very soon) on that.<br>
<br>
++<br>
<span class="HOEnZb"><font color="#888888">Corinne<br>
</font></span><div class="HOEnZb"><div class="h5">On 18 Mar 2014, at 10:47, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
<br>
> 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 :) )<br>
> 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 ?<br>
><br>
><br>
><br>
> On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
><br>
><br>
> On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
> True, eventually we will remove that dependency.<br>
> What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency?<br>
><br>
><br>
> sounds good to me!<br>
><br>
><br>
> ++<br>
> Corinne<br>
> On 18 Mar 2014, at 09:53, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
> > Corinne,<br>
> ><br>
> > no AFN on that project, in the future:<br>
> > <a href="https://issues.jboss.org/browse/AGPUSH-558" target="_blank">https://issues.jboss.org/browse/AGPUSH-558</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
> > Hello Sebi<br>
> ><br>
> > Actually PR are on their ways (as we test it) to set proper version, what you need here<br>
> > <a href="https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile" target="_blank">https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile</a><br>
> > is to upgrade to:<br>
> > platform :ios, ‘7.0'<br>
> > pod 'AFNetworking', ‘2.2.1'<br>
> ><br>
> > Note that we’ll support from ios 7.0<br>
> > Feel free to send the PR with Podfile update if the testing works for you.<br>
> ><br>
> > ++<br>
> > Thanks for the feedback,<br>
> > Corinne<br>
> ><br>
> > On 18 Mar 2014, at 09:44, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
> ><br>
> > > 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)<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Matthias Wessendorf<br>
> ><br>
> > blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> > sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
> > twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
><br>
> --<br>
> Matthias Wessendorf<br>
><br>
> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>