Re: [Gambas-devel] Gambas to Git(Lab)

[PICCORO M. L. <mck...@gm...>]

2017-08-12 3:49 GMT-04:00  <gam...@li...>:
From: "Adrien Prokopowicz" <adr...@gm...>
>> Very strange: 3.10.0 tag is present in the "tags" section of the
>> repository, but not when you pop down the list "switch branch/tag"...
>
> It's there, but the list isn't sorted in natural order, so it's right after
> the 3.1.0 version.

this its due 1.0 its minor rather than 10.0 to amek sense order must
be 3.01.0 vs 3.10.0,

i read the explanation of Adrian, very close to the subversion workflow..

i must added that in git all its technically "virtual" and the
"commits" are always the point of work... unless the directory copy
organization of subversion..

i make a equivalent git page of the
http://gambaswiki.org/wiki/howto/svn as
http://gambaswiki.org/wiki/howto/git with most close tho the svn but
git are de-centralised so unless subversion, a commit its not a
upload.. in git we can made many commits before made an upload.. so
modify as prefer..  i only put info to compilation related

>
> I didn't push the branches for the stable versions, since the tags have the
> same purpose : you can switch to any tag, and create a branch from there if
> you want to make changes to an older version.
>
> (Actually, you can switch to any commit you want and create a branch from
> there :
> commits are kind of like ref-counted, and a tag is just a named reference
> to a
> commit).
>
> However, if I missed something and there is something needed in these
> branches,
> I can push them back.
>
> For tagging new releases, as we've discussed in previous messages, it's
> all done
>  from the "stable" branch : right now it contains the 3.10.0 version, you
> can either
> commit directly to it or cherry-pick commits from the master branch (i.e.
> just take
> specific commits instead of the whole branch, if you want only the
> bugfixes to tag
> a patch release, say 3.10.1).
>
> You can also merge the master branch into stable, which will apply all the
> commits the
> stable branch didn't have, in order to tag a new release, say 3.11.
>
> Once you're done and the stable branch contains what you want to release,
> you just
> have to create an annotated tag[0]. (Annotated tags have checksums and can
> be signed,
> unlike simple tags which are just pointers).
> And then it's done. :-)
>
> [0] https://git-scm.com/book/en/v2/Git-Basics-Tagging
>
> --
> Adrien Prokopowicz
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Gambas-devel mailing list
> Gam...@li...
> https://lists.sourceforge.net/lists/listinfo/gambas-devel
>
>
> ------------------------------
>
> End of Gambas-devel Digest, Vol 113, Issue 2
> ********************************************