[llvm-dev] New LLVM git repository conversion prototype

James Y Knight via llvm-dev llvm-dev at lists.llvm.org
Mon Dec 17 09:01:04 PST 2018


On Thu, Dec 13, 2018 at 12:17 PM Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:

>
>
> On Dec 13, 2018, at 06:30, James Y Knight via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> On Thu, Dec 13, 2018 at 2:06 AM Justin Bogner <mail at justinbogner.com>
> wrote:
>
>> James Y Knight <jyknight at google.com> writes:
>> > On Fri, Nov 16, 2018 at 7:40 PM Jeremy Lakeman <
>> Jeremy.Lakeman at gmail.com>
>> > wrote:
>> >
>> >> Semantic versioning would recommend "v8.0.0-dev", "v8.0.0-rc1" etc. The
>> >> hyphen indicating that this is a pre-release version coming before
>> "v8.0.0"
>> >
>> >
>> > Here's my proposal:
>> > - Release branches will be named: release/3.5.x (for old version
>> numbering
>> > scheme), release/7.x (for new).
>>
>
> I suggest, instead of "release/7.x", that we use "release/7.0.x".  This
> aligns with how we only rev the 3rd part of the tuple when tagging from
> this branch.
>
> In the unexpected case that we have a bugfix that requires an ABI break
> after 7.0.0, we can create "release/7.1.x" for managing those tags.
>

Well, we're facing that unexpected case currently, and AFAIK the plan is to
release 7.0.1, then make the ABI break and release 7.1.0 from the same
branch. I'd expect that to be the case in any such future situation, too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181217/ba279de3/attachment-0001.html>


More information about the llvm-dev mailing list