Re: [aerogear-dev] AeroGear freezing and release dates

On Tue 19 Nov 2013 10:03:13 AM EST, Bruno Oliveira wrote: https://github.com/aerogear/aerogear-android/pull/123, https://github.com/aerogear/aerogear-android/pull/122, * https://github.com/aerogear/aerogear-android/pull/101 This should probably be closed, I don't think we ever reached a conclusion on it before Yavuz went home. * https://github.com/aerogear/aerogear-android/pull/120 I'm conflicted about this on. On the one hand it is a pretty annoying bug. On the other hand the PR still needs a test so we don't unfix it by accident. * https://github.com/aerogear/aerogear-android/pull/122 I think we should try to get this in. It doesn't change any code but it adds the an AAR artifact which we've been wanting to mark as experimental for some time. * https://github.com/aerogear/aerogear-android/pull/123 The big kahuna. I like this and think we should try to merge it, but I agree with abstractj that we should not rush the review process. The APIs have had a lot of review (and made it into iOS) but the code itself has only been a PR for 4 days (three of those days were holidays or weekend). If we bump this, I would like to release it in a 1.3.1 instead of having to wait for the full blown 1.4.0 (which we only have a vague idea of what we want).