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 :-)
Christof
Gesendet: Dienstag, 04. September 2018 um 03:40 Uhr Von: "Miller Puckette" msp@ucsd.edu An: "Christof Ressi" christof.ressi@gmx.at Cc: pd-dev pd-dev@lists.iem.at Betreff: Re: [PD-dev] keep master on github stable
My current policy is only to make branches if I end up having to go back and make bug fixes to 'finished' versions (like 0.48 now) after I've started the scramble for the next version. When this works (that is, when I can avoid having to make bug-fix retrofits) this saves a lot of merging.
The limitation with this policy is that if (for example) you need the key-up bugfix for Mac (which should appear in 0.49 which I hope to release with the newest Tcl/Tk) you have to wait for 0.49 to appear and deal with whatever new bugs it might have. If I can get to a stable 0.49 in the next couple of weeks this should be OK... otherwise I guess I should make a 0.48-3 release which I think will necessitate branching (or maybe not even, if all it ends up needing is a new Tcl/Tk version, hmm).
cheers Miller
On Tue, Sep 04, 2018 at 02:46:43AM +0200, Christof Ressi wrote:
hi, just a small question/suggestion: wouldn't it be better if we keep the current master on github to the last stable release (i.e. 0.48.2) and use a dedicated development branch for adding things?
Christof
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev