search for: r338537

...ase/3.5.x (for old version numbering scheme), release/7.x (for new). > - The tags for release branches will be named v8.0.0 (for final), and v8.0.0-rc1 for release candidates. > - Tags on the master branch (which will be created at commits modifying the version file after branch creation, ala r338537) will be named v8.0.0-dev. I'm not sure about the part about tagging the master branch. In your example, if someone checks out v8.0.0-dev, they would not get the latest version of 8.0.0-dev, i.e. master, but the *first* commit, which seems odd. I suppose we could call it v8.0.0-base or somet...

James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> writes: > On Fri, Nov 16, 2018 at 5:46 PM David Jones <dlj at google.com> wrote: >> $ git tag -m 'Begin development of 8.0.0.' '8.0.0svn' 63297479398 >> >> Then, `git describe` can give a useful result that would be stable(-ish >> [*]): >> >> $ git describe --match=\*svn

...old version numbering > scheme), release/7.x (for new). > - The tags for release branches will be named v8.0.0 (for final), and > v8.0.0-rc1 for release candidates. > - Tags on the master branch (which will be created at commits modifying the > version file after branch creation, ala r338537) will be named v8.0.0-dev. > > On Fri, Nov 16, 2018 at 10:10 PM Justin Bogner <mail at justinbogner.com> > wrote: > >> As a bit of a side note, v8.0.0 is probably too brief - I expect v* >> could easily match some arbitrary tag that starts with the letter v too >&gt...

...version numbering scheme), release/7.x (for new). >> > - The tags for release branches will be named v8.0.0 (for final), and v8.0.0-rc1 for release candidates. >> > - Tags on the master branch (which will be created at commits modifying the version file after branch creation, ala r338537) will be named v8.0.0-dev. >> >> I'm not sure about the part about tagging the master branch. >> >> In your example, if someone checks out v8.0.0-dev, they would not get >> the latest version of 8.0.0-dev, i.e. master, but the *first* commit, >> which seems o...

...ase/3.5.x (for old version numbering scheme), release/7.x (for new). > - The tags for release branches will be named v8.0.0 (for final), and v8.0.0-rc1 for release candidates. > - Tags on the master branch (which will be created at commits modifying the version file after branch creation, ala r338537) will be named v8.0.0-dev. > There haven't been many more responses in the last few days, so can we try to come to some kind of consensus here? I've skimmed through the most recent replies and there 3 things we need to name: 1. Release tags. There were a lot of small variation on th...