Hello,
if the last stable version is V2, there is no reason to set the
master as V1.
The rule must be to set the master on the last stable version, as usual.
So my preference is for c) option with 2.1a.
Thanks
Marc
Le 20/03/2022 à 12:15, Blady via Gnoga-list a écrit :
Hello,
The master branch of the Gnoga GIT repo is stuck on version 1.2a for many years.
Some users point out that, for instance:
"It is customary when using git to have the master branch point at the latest stable
branch. Is there any reason not to for gnoga?" (from Tama)
Thus I propose some options:
a) set master to the last stable V1 commit, that is V1.6a
b) set master to the last V1 commit, that is V1.7-alpha
c) set master to the last stable V2 commit, that is V2.1a
d) set master to the last V2 commit, that is V2.2-alpha
e) add branches named edge, stable...
f) do nothing
My preference is for a).
What is your feedback?
Thanks, Pascal.
https://blady.pagesperso-orange.fr
___
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list
___
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list
