Re: [boost] Git: maintaining super-project

Subject: Re: [boost] Git: maintaining super-project
From: Jeremy Ong (jeremycong_at_[hidden])
Date: 2013-12-04 07:03:40

Maybe I should have said "github" world. Many organizations and open source
projects choose to make it the lowest branch in the hierarchy specifically
because it *is* the default. I wasn't aware that boost uses nvie's gitflow.
There are many that feel it's a bit overengineered, but if it's specified
somewhere that that is what we're using then eschewing the defaults is fine.

On Wed, Dec 4, 2013 at 6:46 AM, Mateusz Loskot <mateusz_at_[hidden]> wrote:

> On 4 December 2013 11:36, Jeremy Ong <jeremycong_at_[hidden]> wrote:
> > In the git world, it's more common for develop to occur on "master" and
> for
> > set releases to go to a "release" branch (with tags).
>
> In the git world, "master" is nothing else than just a default branch.
>
> In the git world, you *never* do development on "master", but a topic
> branch.
>
> In the git world, "master" is not equivalent to SVN trunk, but again,
> it's just a default branch.
> How you treat your default branch (latest vanilla upstream or latest
> stable or any other way),
> depends on a workflow of your choice.
>
> In the git world, numerous (or hardly finite number) workflows are
> possible, all are equally valid.
>
> Boost uses gitflow.
>
> Best regards,
> --
> Mateusz  Łoskot, http://mateusz.loskot.net
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>