On Tue, Oct 7, 2014 at 5:02 PM, Corinne Krych <corinnekrych(a)gmail.com>
+1 on having aerogear-ios be our umbrella repo.
Master to list our different 2.0 repos maybe to start with just README.
Once we've got cocopoads we can think of some think like a
not sure :) but if the community goes w/ that, let's do what's natural there
Another topic is to switch 'swift' branch to master and create a 'obj-c'
branch with obj-c code for repo like ios-push, ios-cookbook,
+1 on Swift going to master
and have 1.x.y branches and.... for maintenance let's do objc branch(es) as
Do we all agree on that?
On 7 October 2014 16:07, Matthias Wessendorf <matzew(a)apache.org> wrote:
> On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak(a)gmail.com>
>> Hi all,
>> as we approach 2.0 releases in iOS we are evaluating the faith of our
>> 1.x repository . Currently the functionality has been splitted in
>> separate repositories with more to come in subsequent releases .
>> Since other platforms follow the same approach of separation, would like
>> to get your view on how you will handle the ‘1.x’ repo?
>> We were thinking to:
>> a) promote the master repo to an '1.x branch’ and update the repos
>> README.md to be clear that is our 1.x branch
>> b) use the ‘master’ branch with just a single README.md that provides
>> links to the different repos.
> Do you mean, the repo in  will be just a readme, linking to all the
> different 'modules'? If so, +1 on that
>>  https://github.com/aerogear/aerogear-ios
>>  https://github.com/aerogear/aerogear-ios-http
>>  https://github.com/aerogear/aerogear-ios-oauth2
>> aerogear-dev mailing list
> Matthias Wessendorf
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> aerogear-dev mailing list
aerogear-dev mailing list