Not sure how you guys are doing it here,

But some people recommend keeping the master branch stable and doing
new development / patches in other branches. Merging is a breeze with
git so usually when i work on features i do it in a new feature branch
for that specifically, then when i'm tested and working with it, i
merge it into my master banch.


On 29 January 2014 21:40, Michele Calgaro <michele.calgaro@...> wrote:
>> Source changes will be restricted to Blocker/Critical bug fixes only.
>> Documentation changes will be restricted at the RC2 phase, similar to how
>> Ubuntu handles releases.
>
> Thanks Tim.
> So at the same time are we starting a separate branch for RC1 so we are still free to work on the main trunk on other things?
>
>   Michele
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>