Re: [Tiki-devel] Tag ambiguity

Jonny Bradley via TikiWiki-devel <[email protected]>
Newsgroups gmane.comp.cms.tiki.devel
Message-ID <[email protected]>
Hi P-M again

I have no real idea, sorry, but it's probably connected with when we moved to gitlab as the main repo, i think 18.x and 19.x were branched on sf.net in svn, and after that we moved to using git first, possibly 18.8 was the first 18.x release using git... Roberto/Fabio does that sound right?

jb



> On 22 Apr 2021, at 23:22, Polyna-Maude Racicot-Summerside <[email protected]> wrote:
> 
> Hi,
> 
> There seem to be a problem with some tags not being published properly.
> 
> Example...
> 
> If you do
> 
> git tag | grep '18'
> 
> you'll see the following
> 
> 18.0
> 18.0alpha
> 18.0beta
> 18.1
> 18.2
> 18.3
> 18.4
> tags/18.8
> 
> Why does 18.8 gets under the tags namespace and not the other ones ?
> 
> and now if we do the same with 21
> 
> git tag | grep '21'
> 
> tags/21.0
> tags/21.0RC1
> tags/21.0beta
> tags/21.1
> tags/21.2
> tags/21.3
> tags/21.4
> 
> for 22
> 
> git tag | grep '22'
> 
> tags/22.0
> tags/22.0RC1
> tags/22.0alpha
> tags/22.0beta
> tags/22.1
> 
> for 20 we get (stange again)...
> 
> git tag | grep '20'
> 
> 20.0
> 20.0RC1
> 20.0alpha
> 20.0beta
> 
> for 19 we get
> 
> git tag | grep '19'
> 
> 19.0
> 19.0RC1
> 19.0alpha
> 19.0beta1
> 19.1
> 19.2
> 
> So the change seem to one that happened around a specific date.
> 
> The 18.x series was edited in last January and this created the tags/18.8
> 
> Now if we list all the ones that are under tags we get :
> 
> tags/18.8
> tags/21.0
> tags/21.0RC1
> tags/21.0beta
> tags/21.1
> tags/21.2
> tags/21.3
> tags/21.4
> tags/22.0
> tags/22.0RC1
> tags/22.0alpha
> tags/22.0beta
> tags/22.1
> 
> For sure, it's better to have the tags under the tags namespace so it can't cause some ambiguity with a branch having the same name.
> 
> So it would be best if all the future tags are done under the tags namespace.
> 
> This is my personal opinion...
> 
> Can this be caused by the bridge used to sync with SVN ?
> 
> 
> 
> -- 
> Polyna-Maude R.-Summerside 
> https://www.polynamaude.com/ 
> 
> -Be smart, Be wise, Support opensource development
> 
> Mise en garde concernant la confidentialité
> 
> La présente communication est confidentielle et transmise sous le sceau du
> secret professionnel. Si vous n’êtes pas le destinataire visé ou son
> mandataire chargé de lui transmettre cette communication, vous êtes par
> les présentes avisées qu’il est expressément interdit d’en dévoiler la 
> teneur, de la copier, de la distribuer ou de prendre quelques mesures 
> fondées sur l’information qu’il y est contenu. Si vous aviez reçu cette 
> communication, par erreur, veuillez nous en aviser immédiatement par 
> téléphone (frais virés) et nous retourner l’original sans tirer ni garder 
> de copie, soit par la poste à l’adresse ci-haut mentionnée. 
> 
> Confidentiality Notice
> 
> The information in this transmission may contain 
> privileged and confidential information and is intended only for the use 
> of the person or corporate entity to which it is addressed. The 
> confidential nature of this communication remains regardless of whether or
> not you are an intended recipient. If you are not an intended recipient, 
> please notify the sender immediately and destroy this message and all 
> attachments, without making a copy. Any distribution or reproduction of 
> this message is prohibited. We assume no liability for the interception of
> any Internet communication or the transmission of computer viruses.
> 
> CP 99900 FJ 782 595
> SUCC ST- DOMINIQUE
> MONTRÉAL QC H2S 0E3
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel



_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.