Re: [aerogear-dev] Handling 1.x repositories

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.

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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev