View Issue Details

IDProjectCategoryView StatusLast Update
0000288Cinelerra-GG[All Projects] Featurepublic2019-09-02 20:09
Reporterferdnyc Assigned Togoodguy  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionfixed 
Product Version 
Target VersionFixed in Version2019-08 
Summary0000288: Request: Tag "version update" commits in git repo
DescriptionWhen doing the monthly "version update" in the git repo, would it be possible in the future to to `git tag` those commits? It'd make it easier to check out the tree at exactly that point.
TagsNo tags attached.

Activities

PhyllisSmith

PhyllisSmith

2019-08-31 22:02

manager   ~0002057

OK, the tag has been added and is visible. Not marking this Closed yet in case there is a problem because once it is Resolved or Closed, no one can add a note anymore. Will close in a couple of days instead.
ferdnyc

ferdnyc

2019-08-29 17:31

reporter   ~0002051

Thanks, Phyllis! Really anything's /acceptable/, the system used is entirely up to the developers.

For clarity and simplicity, my suggestion would be to stick with the same version strings used in MantisBT:
2019-07, 2019-08, etc. Those are perfectly fine tags.

(If nothing else, I'd strongly suggest some variation on ISO-8601 YYYY-MM-DD ordering, to avoid the ambiguity of dd/mm-vs-mm/dd.)
PhyllisSmith

PhyllisSmith

2019-08-29 16:15

manager   ~0002050

ferdnyc:
I am recommending to GG to use something similar to (mostly because it will be easy and obvious to him):
  git tag -a 08-31-2019 -m "version update"

As you have already found out, we are not "build meisters" and handle several distros that seem to do things differently so do not know what a more standard tag might be. If you have a recommendation, we can certainly consider it, but I am pretty sure something like "-a v5.1.20" will not be acceptable to gg and sometimes it is difficult for me to convince him!
PhyllisSmith

PhyllisSmith

2019-08-29 15:49

manager   ~0002049

Sounds simple enough from what I read about "git tag". I will have GG try it on the August 31 builds to make sure it really is easy and will respond here if/when that happens.

Issue History

Date Modified Username Field Change
2019-08-29 15:12 ferdnyc New Issue
2019-08-29 15:49 PhyllisSmith Note Added: 0002049
2019-08-29 15:49 PhyllisSmith Assigned To => goodguy
2019-08-29 15:49 PhyllisSmith Status new => assigned
2019-08-29 15:50 PhyllisSmith Status assigned => acknowledged
2019-08-29 16:15 PhyllisSmith Status acknowledged => feedback
2019-08-29 16:15 PhyllisSmith Note Added: 0002050
2019-08-29 17:31 ferdnyc Note Added: 0002051
2019-08-29 17:31 ferdnyc Status feedback => assigned
2019-08-31 22:02 PhyllisSmith Status assigned => confirmed
2019-08-31 22:02 PhyllisSmith Note Added: 0002057
2019-09-02 20:09 PhyllisSmith Status confirmed => closed
2019-09-02 20:09 PhyllisSmith Resolution open => fixed
2019-09-02 20:09 PhyllisSmith Fixed in Version => 2019-08