<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 5, 2014 at 9:33 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">Moving to 2.0 for AFNetworking is a great idea.<br>
it may quite an impact though.<br>
When are we planning 1.4?<br></blockquote><div><br></div><div>I'd agree that moving to AFN2 should be done after 1.4.</div><div>I think in an older meeting (or email thread), we already talked about getting 1.4 out, update to AFN2 (call it 1.5) and than continue w/ 'scheduled' work (e.g. sync) for 1.6</div>
<div><br></div><div><br></div><div>-M</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
++<br>
<span class="HOEnZb"><font color="#888888">Corinne<br>
</font></span><div class="HOEnZb"><div class="h5">On 05 Feb 2014, at 09:28, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> I have been thinking that as part of this change[1] of target the lib to iOS 7, in the process updating the internal AFNet lib to 2.0 series also which is optimised for iOS 7. Not sure if I can pause it till our next release or be included in 1.4?<br>
><br>
> wdyth?<br>
><br>
> -<br>
> Christos<br>
><br>
> [1] <a href="https://issues.jboss.org/browse/AGIOS-152" target="_blank">https://issues.jboss.org/browse/AGIOS-152</a><br>
><br>
> On Jan 16, 2014, at 12:57 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
>><br>
>><br>
>><br>
>> On Thu, Jan 16, 2014 at 9:21 AM, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
>><br>
>> On Jan 16, 2014, at 8:31 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>><br>
>>> Hi,<br>
>>><br>
>>> in December, while I was away, I missed an email from Apple Developer, telling that by Feb. 1st all app submissions to the store need to be 'optimized' for iOS 7.<br>
>>><br>
>>> "Starting February 1, new apps and app updates submitted to the App Store must be built with the latest version of Xcode 5 and must be optimized for iOS 7. "<br>
>>><br>
>>><br>
>>> That's an interesting statement; also for our iOS libraries... - So.... looks like we can simply remove the 'support' / linkage of older SDKs, and straight update to iOS 7...<br>
>>><br>
>>> Thoughts ?<br>
>><br>
>> IMHO it makes sense to move +1<br>
>><br>
>> What do you think of creating a JIRA for 'optimizing iOS libraries for iOS7" ?<br>
>> After the 1.4.0 is released, we could do that task, release a 1.5.0 and move on with other items (e.g. like sync)<br>
>><br>
>><br>
>> -Matthias<br>
>><br>
>><br>
>><br>
>><br>
>> -<br>
>> Christos<br>
>><br>
>><br>
>>> -Matthias<br>
>>><br>
>>> [1] <a href="https://developer.apple.com/news/" target="_blank">https://developer.apple.com/news/</a><br>
>>> [2] <a href="http://techcrunch.com/2013/12/17/apple-requiring-all-app-submissions-to-be-optimized-for-ios-7-by-feb-1st/" target="_blank">http://techcrunch.com/2013/12/17/apple-requiring-all-app-submissions-to-be-optimized-for-ios-7-by-feb-1st/</a><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>
>> 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>