I had the very same problem when I first tried Gnoga. I simply checked
out the master branch expecting the latest development.
I therefore vote for (d). Having the incompatibilities from
internationalisation we can also call the latest V1 commit the stable
branch. Master doesn't necessarily mean stable. It means newest in most
of the public projects that I know.
regards
Rolf
Am 20.03.2022 um 12:15 schrieb Blady via Gnoga-list:
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
