On 8/22/14 11:15 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> Agreed, and so, lesson learned: this is why we do need to cut release >> branches even if there isn't much going on in develop branch. Or would >> the release branch also contain these blazeDS and the merge would have >> tired to merge them? >A release branch would of been of little help here. The issue is that we >have several projects in a git repo each under their own directory and >git prefers one project per repo. Should we ask for more repos? Or maybe just one where new donations go until released? -Alex
