6:25 a.m.
Hey guys,
on yesterday's Aerogear.js meeting we have discussed in which version we
should include Data Sync module. Since we are starting works on ES6
compatibility, which is one of the big features for 2.0, it make sense to
continue with Data Sync there.
What about Android and iOS SDKs? Do you plan to include new module in 2.0
or start that in 1.x and later backport to 2.0?
Cheers!
~ Lukas
7:18 a.m.
Hello Lukas
For iOS, I initially planned as part of 2.2 (November), see roadmap:
http://aerogear.org/docs/planning/roadmaps/AeroGeariOS/
but looking at finalize roadmap
https://github.com/aerogear/aerogear.org/blob/data-sync-rebirth-roadmap/d...
I think i’m going to move AGIOS-266 and AGIOS-267 in 2.1 (October) so that it matches both
roadmap. Specially we did some work already on Conflict reolution here:
https://github.com/corinnekrych/aerogear-diff-patch-ios
We’ll need to revisit it in Swift off course. Let me do a PR for iOS roadmap.
++
Corinne
On 19 Sep 2014, at 13:25, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
Hey guys,
on yesterday's Aerogear.js meeting we have discussed in which version we should
include Data Sync module. Since we are starting works on ES6 compatibility, which is one
of the big features for 2.0, it make sense to continue with Data Sync there.
What about Android and iOS SDKs? Do you plan to include new module in 2.0 or start that
in 1.x and later backport to 2.0?
Cheers!
~ Lukas
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
8:45 a.m.
On Sep 19, 2014, at 8:18 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
Hello Lukas
For iOS, I initially planned as part of 2.2 (November), see roadmap:
http://aerogear.org/docs/planning/roadmaps/AeroGeariOS/
have we discussed yet when 2.0 will start?
but looking at finalize roadmap
https://github.com/aerogear/aerogear.org/blob/data-sync-rebirth-roadmap/d...
I think i’m going to move AGIOS-266 and AGIOS-267 in 2.1 (October) so that it matches
both roadmap. Specially we did some work already on Conflict reolution here:
https://github.com/corinnekrych/aerogear-diff-patch-ios
We’ll need to revisit it in Swift off course. Let me do a PR for iOS roadmap.
++
Corinne
On 19 Sep 2014, at 13:25, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
> Hey guys,
>
> on yesterday's Aerogear.js meeting we have discussed in which version we should
include Data Sync module. Since we are starting works on ES6 compatibility, which is one
of the big features for 2.0, it make sense to continue with Data Sync there.
>
> What about Android and iOS SDKs? Do you plan to include new module in 2.0 or start
that in 1.x and later backport to 2.0?
>
>
> Cheers!
>
> ~ Lukas
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
8:20 a.m.
On 9/19/2014 7:25 AM, Lukáš Fryč wrote:
Hey guys,
on yesterday's Aerogear.js meeting we have discussed in which version
we should include Data Sync module. Since we are starting works on ES6
compatibility, which is one of the big features for 2.0, it make sense
to continue with Data Sync there.
What about Android and iOS SDKs? Do you plan to include new module in
2.0 or start that in 1.x and later backport to 2.0?
It will be part of 2.0. We
don't have any plans to back port this to
the 1.x branches of things.
Passos, feel free to correct me if I am wrong.
Cheers!
~ Lukas
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
12:50 p.m.
Summers you're never wrong :)
BTW, I'm not sure about 2.0 or 2.1, we are in the middle of a BIG
refactoring for 2.0
-- Passos
On Fri, Sep 19, 2014 at 10:20 AM, Summers Pittman <supittma(a)redhat.com>
wrote:
On 9/19/2014 7:25 AM, Lukáš Fryč wrote:
Hey guys,
on yesterday's Aerogear.js meeting we have discussed in which version we
should include Data Sync module. Since we are starting works on ES6
compatibility, which is one of the big features for 2.0, it make sense to
continue with Data Sync there.
What about Android and iOS SDKs? Do you plan to include new module in
2.0 or start that in 1.x and later backport to 2.0?
It will be part of 2.0. We don't have any plans to back port this to the
1.x branches of things.
Passos, feel free to correct me if I am wrong.
Cheers!
~ Lukas
_______________________________________________
aerogear-dev mailing
listaerogear-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
8:17 a.m.
On Friday, September 19, 2014 1:50:33 PM, Daniel Passos wrote:
Summers you're never wrong :)
BTW, I'm not sure about 2.0 or 2.1, we are in the middle of a BIG
refactoring for 2.0
Can we make a areogear-android-datasync:0.1 then?
-- Passos
On Fri, Sep 19, 2014 at 10:20 AM, Summers Pittman <supittma(a)redhat.com
<mailto:supittma@redhat.com>> wrote:
On 9/19/2014 7:25 AM, Lukáš Fryč wrote:
> Hey guys,
>
> on yesterday's Aerogear.js meeting we have discussed in which
> version we should include Data Sync module. Since we are starting
> works on ES6 compatibility, which is one of the big features for
> 2.0, it make sense to continue with Data Sync there.
>
> What about Android and iOS SDKs? Do you plan to include new
> module in 2.0 or start that in 1.x and later backport to 2.0?
It will be part of 2.0. We don't have any plans to back port this
to the 1.x branches of things.
Passos, feel free to correct me if I am wrong.
>
>
> Cheers!
>
> ~ Lukas
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
8:27 a.m.
On Mon, Sep 22, 2014 at 10:17 AM, Summers Pittman <supittma(a)redhat.com>
wrote:
On Friday, September 19, 2014 1:50:33 PM, Daniel Passos wrote:
> Summers you're never wrong :)
>
> BTW, I'm not sure about 2.0 or 2.1, we are in the middle of a BIG
> refactoring for 2.0
>
Can we make a areogear-android-datasync:0.1 then?
Sure
-- Passos
>
> On Fri, Sep 19, 2014 at 10:20 AM, Summers Pittman <supittma(a)redhat.com
> <mailto:supittma@redhat.com>> wrote:
>
> On 9/19/2014 7:25 AM, Lukáš Fryč wrote:
>
>> Hey guys,
>>
>> on yesterday's Aerogear.js meeting we have discussed in which
>> version we should include Data Sync module. Since we are starting
>> works on ES6 compatibility, which is one of the big features for
>> 2.0, it make sense to continue with Data Sync there.
>>
>> What about Android and iOS SDKs? Do you plan to include new
>> module in 2.0 or start that in 1.x and later backport to 2.0?
>>
> It will be part of 2.0. We don't have any plans to back port this
> to the 1.x branches of things.
> Passos, feel free to correct me if I am wrong.
>
>>
>>
>> Cheers!
>>
>> ~ Lukas
>
>
3518
days inactive
3521
days old
6 comments
5 participants
participants (5)
-
Corinne Krych -
Daniel Passos -
Lucas Holmquist -
Lukáš Fryč -
Summers Pittman