Re: [Hamlib-developer] 4.6.3 and 4.7.0 releases plan

[Daniele F. <iu...@gm...>]

Hello,

I'm also ok with a 4.6.3 now. I have 3 PRs in draft which are more
suitable for 4.7 or later because they involve changes in the builds.

> Yes, I plan to create a 4.6.3 branch off master.  In the future I hope
> to get back to having a branch such as "4.7"

creating a stable branch makes it easier for contributors to send pull
requests to fix small bugs, being small, they are probably easy to
cherry-pick in the development branch.

> This is probably an area that could be improved so I'm open to ideas on
> how best to have PRs integrate into an existing stable branch and the
> master development branch.

one possible workflow is to accept in the stable branch only fixes
that improve stability (eg. parameter checking or error handling);
changes to the documentation could also go in stable if they improve
the life of downstream maintainers or users; changes related to
firmwares probably need a decision on a case by case basis.

What would be the name of the development branch? I have a slight
preference for a fixed name such as devel or next (o something else)
versus a numbered name, because it can create ambiguity until it's
released (eg. if we had Hamlib-4.6.23 and Hamlib-4.7 it wouldn't be
clear if 4.7 is stable or not)

-- 
73 de IU5HKX Daniele