[aerogear-dev] Handling 1.x repositories

[Matthias Wessendorf]

On Tue, Oct 7, 2014 at 5:02 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> +1 on having aerogear-ios be our umbrella repo.
>
> Master to list our different 2.0 repos maybe to start with just README.
>
+1


> Once we've got cocopoads we can think of some think like a subpod.
>

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
well


>
> Do we all agree on that?
>
> ++
> Corinne
>
>
> On 7 October 2014 16:07, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>> On Tue, Oct 7, 2014 at 3:21 PM, Christos Vasilakis <cvasilak at gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> as we approach 2.0 releases in iOS we are evaluating the faith of our
>>> 1.x repository [1]. Currently the functionality has been splitted in
>>> separate  repositories[2][3] 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 [1] will be just a readme, linking to all the
>> different 'modules'? If so, +1 on that
>>
>>
>>>
>>>
>>> Wdyth?
>>>
>>>
>>> -
>>> Christos
>>>
>>>
>>> [1] https://github.com/aerogear/aerogear-ios
>>> [2] https://github.com/aerogear/aerogear-ios-http
>>> [3] https://github.com/aerogear/aerogear-ios-oauth2
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/e9807477/attachment.html