As much as I could follow, It's been more about that master should be stable, 
such that all (unstable) branches come from it.  That's the reverse of old 
CVS/SVN practice in which forking was discouraged.  Most have moved to a modern 
mindset such that forking often is good, therefore master should be stable.

________________________________
From: boinc_dev <boinc_dev-boun...@ssl.berkeley.edu> on behalf of Robert Miles 
<robertmi...@bellsouth.net>
Sent: Wednesday, 9 August 2017 00:05
To: boinc_dev@ssl.berkeley.edu
Subject: [boinc_dev] Subject: Re: Software development and branches, was Re:, 
[boinc_projects] keywords

Are people here disagreeing on whether a previous version of master
should be retained and marked
stable when a bug fix is imported into master?  That should allow
testing of new bug fixes against a
stable version of master.
> Date: Mon, 7 Aug 2017 23:23:55 -0700
> From: David Anderson <da...@ssl.berkeley.edu>
> To: Bernd Machenschalk <bernd.machensch...@aei.mpg.de>,
>        boinc_dev@ssl.berkeley.edu
> Subject: Re: [boinc_dev] Software development and branches, was Re:
>        [boinc_projects] keywords
>
> Please read
> https://boinc.berkeley.edu/trac/wiki/SoftwareTesting
> -- David
>
> On 8/7/2017 10:28 PM, Bernd Machenschalk wrote:
>> On 07.08.17 21:40, David Anderson wrote:
>>> I've proposed creating server release branches,
>>> similar to the exiting client release branches.
>>> Hopefully this will satisfy everyone's needs.
>> What I (and others) need is a "stable" branch (whatever named) I can
>> - branch off my own development to work without being affected by others
>> - compare and test my changes against, which requires that the original 
>> branch is
>> "stable"
>> - merge my development (branch) into when I'm done and I and others are 
>> convinced
>> that my development does what it should and doesn't destabilize the branch.
>>
>> I don't see how server release branches would do that.
>>
>> Bernd


_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to