Home > open-source, PlanetCDOT, programming > Successful Git Branching Model

Successful Git Branching Model

While looking around the #paladin wiki (https://wiki.mozilla.org/Paladin), I’ve run into this:


This link is featured on the paladin/workflow wiki page. It talks about a release/development model that center’s around Git’s cheap branches.

Now I’ve had some experience with mercurial before but I’m quite new to the Git way of “doing things” so I’m wondering, what is the typical/accepted way of “versioning” in the Git world and how different is this proposed model from what is considered mainstream?

Thank you for your attention, I apologize in advance if this post is way too newbie for consideration J

  1. September 15, 2011 at 10:18 pm

    The neat thing about git is that it doesn’t force you into any particular development or versioning model. You’re free to choose your own. Pretty much all of the open source projects that use git tend to follow the git-flow process described at that link, to some extent. It’s very prescriptive, but you don’t need to follow everything they do.

    • northwind87
      September 15, 2011 at 11:11 pm

      Ok that sounds cool. Back when I used to use merc on a day to day basis, it was pretty much whatever goes; perhaps I was missing out on some kind of “merc-flow” that could have acted as a kind of starting block for me. In any case, thank you for the explanation, I appreciate your expertise 🙂

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: