[PD-dev] keep master on github stable

Christof Ressi christof.ressi at gmx.at
Tue Sep 4 10:22:01 CEST 2018

Hi Dan,

thanks for your explanation!

Gesendet: Dienstag, 04. September 2018 um 09:41 Uhr
Von: "Dan Wilcox" <danomatika at gmail.com>
An: "Christof Ressi" <christof.ressi at gmx.at>, "Miller Puckette" <msp at ucsd.edu>
Cc: pd-dev <pd-dev at lists.iem.at>
Betreff: Re: [PD-dev] keep master on github stable

OpenFrameworks initially keep the master branch on the latest stable release and used a develop branch for active work. However, this led to many situations where submitters inadvertently did work on their copy of the develop branch and submitted PRs to the master branch. This led to all sorts of issues, especially to newer developers starting out with git. Thankfully it's *much* easier to change the PR branches now, but it still leads to confusion.
For a project where users *only* really build the source code (ie. software libraries), then the "master as stable" approach is useful as it means the default clone is always stable. For projects where the majority of users download pre-built binaries (ie. Pd), I think "master as develop" makes sense since most people cloning will be building/developing the software and those that aren't can checkout a stable tag. So the emphasis is based on the predominant use case: in the former, the master as the release and the latter uses master as develop.
On Sep 4, 2018, at 4:53 AM, pd-dev-request at lists.iem.at[mailto:pd-dev-request at lists.iem.at] wrote: 
Date: Tue, 4 Sep 2018 04:52:58 +0200
From: "Christof Ressi" <christof.ressi at gmx.at[mailto:christof.ressi at gmx.at]>
To: "Miller Puckette" <msp at ucsd.edu[mailto:msp at ucsd.edu]>
Cc: pd-dev <pd-dev at lists.iem.at[mailto:pd-dev at lists.iem.at]>
Subject: Re: [PD-dev] keep master on github stable
<trinity-24063e5f-6755-4798-b27d-4d08994e7ee5-1536029578754 at 3c-app-gmx-bs59>

Content-Type: text/plain; charset=UTF-8

I see. The reason I was asking is that many OSS projects have both master and develop branches so people can choose between the latest stable version and the newest stuff (accepting possible regressions). So all the real work would happens on the develop branch and whenever a release is out (after the feedback and bug fixes from the test releases) the master branch gets updated. but this is just an idea for the future. don't bother now :-)


Dan Wilcox

More information about the Pd-dev mailing list