Outside view.  The misunderstandings appear to originate in the purpose of GiT 
in the first place:

- CVS/SVN --> Forking is bad, Don;t fork, Head is for active development, tags 
for snapshots, branching is like theft.  Dilution of the developer base

- Git --> Forking is good, fork and fork often.  Merge back proven things.


The first case stifles development through notions of control, common through 
the Boinc codebase in black and white.  The second case encourages development, 
biologically/genetically.


Having used both approaches, I'd recommend a mindset shift toward the newer 
mechanism.


------------------------------------------------------------------------------------------------------
Jason Richard Groothuis
bSc(compSci)
------------------------------------------------------------------------------------------------------


________________________________
From: boinc_dev <boinc_dev-boun...@ssl.berkeley.edu> on behalf of Bernd 
Machenschalk <bernd.machensch...@aei.mpg.de>
Sent: Tuesday, 8 August 2017 14:58
To: David Anderson; boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev] Software development and branches, was Re: 
[boinc_projects] keywords

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