[llvm-dev] New LLVM git repository conversion prototype

[David Greene via llvm-dev]

David Jones <dlj at google.com> writes:

> (Just a side note: "split" seems ambiguous to me, in the sense of
> whether it's before or after the branch is cut: does it point to the
> start-point of the release branch? Or does it point to the commit that
> bumps the version number

Yeah.  We actually tag the start-point of the release branch and name it
v<old>-v<new>-split, but that's wordy and not very good for LLVM or
probably anyone else, really.  :)

I don't really care about the name, just adding to the bikeshedding by
giving another option.

> I like Duncan's suggestions for release naming, and I could imagine
> something like:
>
> tags/llvm.org/v8.X.Y - development
> tags/llvm.org/release/v8.0.0-rc1 - release candidate

I kind of like this.

> heads/llvm.org/release_80 or heads/llvm.org/release/v8.0 - release
> branch (the former matches existing branch names)

Do we need "llvm.org" or "release" in branch names?  Are we likely to
have many "official" branches beyond master and release branches?
Downstream can always "remap" upstream branches (master ->
upstream_master) or namespace their own branches "cray/release_X."  You
can't do that with tags which is why tag names need disambiguation.

                          -David