Re: [Hamlib-developer] github vs sourceforge, branches?

[Nate B. <n0...@n0...>]

* On 2022 10 Nov 06:51 -0600, Greg Troxel wrote:
> 
> It would really help if README (and I mean top level, not some
> developer-only one) answered:

Historically, the intended audience of the README file is that which
received the source tarball.  In recent years its scope has expanded,
but too much information can be as confusing as too little is
frustrating.

>   What is the authoritative home for hamlib: github, sourceforge,
>   someplace else?

Actually, both SourceForge and GitHub have equal standing as far as
versioned releases are concerned.

>   In each git repo that has any standing (vs mirrors), what do the
>   branches mean?
> 
> The second can be as brief as "Development happens on master (often by
> merging feature branches) and each release has a release branch."

This last paragraph sums it up, development occurs in the master branch
with feature branches merged in as appropriate.  Release branches are
named 'Hamlib-M.m[.p]' where M is the major version, m is the minor
version, and the optional p is the point release version.

Any other branches are likely historical relics from the CVS/SVN days
and can be safely ignored.  Currently feature branches mostly exist in
personal working repositories and then are merged into master.

As far as development goes, GitHub is the primary development platform
these days.  I sync the SourceForge master branch manually on occasion
from the GitHub master branch.  Unfortunately, this is not done every
day and it will sometimes lag by several weeks depending on when I get
around to it.  Release branches are pushed to each as part of my release
procedure.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819