Re: [Gnoga-list] GIT master branch discussion.
I vote d. That was how it was originally and what I think most expect. On Sun, Mar 20, 2022 at 7:16 AM Blady via Gnoga-list < gnoga-list@lists.sourceforge.net> wrote: > 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
Re: [Gnoga-list] GIT master branch discussion.
Hi Pascal I vote (d) for the reasons expressed by Rolf. d) too cause this is the (informal) standard... i.e. the way most people understand that. -- Stéphane Rivière Ile d'Oléron - France OpenPGP_0x68A4C5C1D498F92F.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
Hello Pascal, I vote (d) for the reasons expressed by Rolf. Cheers, Gautier *From:* Blady *Sent:* Dimanche, Mars 20, 2022 12:15PM *To:* Gnoga-List *Cc:* David Botton , Jeffrey R. Carter , David Botton , Gdemont *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
