Hello Pascal,
I vote (d) for the reasons expressed by Rolf.
Cheers,
Gautier
------------------------------------------------------------------------
*From:* Blady <blady-...@users.sf.net>
*Sent:* Dimanche, Mars 20, 2022 12:15PM
*To:* Gnoga-List <gnoga-list@lists.sourceforge.net>
*Cc:* David Botton <da...@botton.com>, Jeffrey R. Carter
<jc...@ymail.com>, David Botton <dbot...@users.sourceforge.net>, Gdemont
<gdem...@hotmail.com>
*Subject:* GIT master branch discussion.
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
