If we decide to go down this path, we should sort of have a standard fort he
main subproject branch.
I would suggest "develop-{subproject-name}".
This way all develop branches should be sorted and visible together and you
don't have to check if it's just a feature branch of something else.
Is Radii8 something major? If yes an own repo would be a good idea ... if it's
just an addition to something, I would vote for the utils with its own branch.
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aha...@adobe.com]
Gesendet: Sonntag, 31. August 2014 07:49
An: dev@flex.apache.org
Betreff: Re: How to manage flex-utilities git repo
OK, so should I ask Infra for flex-radii8 or do we want to try this idea on it?
If I understand, I would create a radii8 branch and check the code in there?
-Alex
On 8/30/14 10:05 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>I like it.
>
>On Aug 30, 2014, at 6:13 PM, Christofer Dutz
><christofer.d...@c-ware.de>
>wrote:
>
>> Hi,
>>
>> while working on Squiggly, FlexPMD and the Mavenizer I too realized
>>that the way we are currently doing things here is far from ideal as
>>merging stuff back to master is allmost impossible.
>>
>> How about not having a "develop" branch, but one for each sub-project.
>>So when I start working on the mavenizer, I checkout "develop-mavenizer"
>>and branch from that. As soon as my feature is finished, I merge my
>>stuff from my feature branch back to "develop-mavenizer" now ... when
>>a new version of the mavenizer is done, all I have to do, is merge
>>everything oft he "develop-mavenizer" branch to master and don't have
>>to think about what's in and what's not.
>>
>> Just a thought ...
>>
>> Chris
>
