On 04/08/17 12:10 , Richard Haselgrove wrote:
> In that case, the workflow document linked by David earlier
> - https://boinc.berkeley.edu/trac/wiki/AdminReleaseManagement - contains
> totally unnecessary extra work steps:

Indeed.

> * Clone branch: clone ​https://github.com/boinc/boinc.git into new dir
> w/ version num

The wording "clone branch" is at least confusing and even wrong when
read out of context. The line is incomplete and inconsistent.

Also, using TortoiseGit (being a Windows Explorer context menu
extension) as the canonical example isn't a good choice. One should use
platform independent descriptions that help everyone. The git CLI or
even GUIs like GitKraken and SourceTree are certainly better suited for
that purpose.

But first things first. These issues can be addressed in a general overhaul.

> * android: TODO; Oliver: textual representation, numerical value (increment) 
> in 7.6, it's 146, so use 147
FYI, that's already been taken care of (for Android at least) via:
https://github.com/BOINC/boinc/issues/1864

The desktop manager's still pending though.

> The only reasons I can see for creating a new directory are:
> To create clean build folders for the development tools to work in

Yes, but even that is not necessary. You can (and should) always check
for and handle untracked files using "git status" (ignore or add them).
You may also stash away pending working tree changes using "git stash".
Working in multiple copies of a repo can be more confusing to beginners
than sticking to a single one that's properly managed.

> To create an offsite archival backup in case of disaster

No. If you want your local repo backed up, just push it to a remote of
your choice. Typically that's your personal fork on GitHub.

Cheers,
Oliver

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
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