[Mesa-dev] Releasing 18.0

[Michel Dänzer]

On 2018-03-15 08:21 PM, Marek Olšák wrote:
> On Thu, Mar 15, 2018 at 2:34 PM, Michel Dänzer <michel at daenzer.net
> <mailto:michel at daenzer.net>> wrote:
> 
>     On 2018-03-15 07:25 PM, Marek Olšák wrote:
>     > On Thu, Mar 15, 2018 at 2:19 PM, Michel Dänzer <michel at daenzer.net <mailto:michel at daenzer.net>
>     > <mailto:michel at daenzer.net <mailto:michel at daenzer.net>>> wrote:
>     >
>     >     On 2018-03-15 06:01 PM, Marek Olšák wrote:
>     >     >
>     >     > pick a3ac60e ac: move address space definitions to common code
>     >     > pick 572d46d ac: Use the renumbered const address space for LLVM 7.
>     >     > # Both are convenient for AMD devs testing 18.0 with LLVM master. The
>     >     > latter depends on the former.
>     >
>     >     It's not realistic to keep the 18.0 branch working with LLVM SVN trunk
>     >     in the long term, I'd suggest not even bothering.
>     >
>     >
>     > It's as realistic as keeping master working. Since LLVM 7 will be frozen
>     > in 5 months, it's very realistic that this or a future point release of
>     > 18.0 will work with LLVM 7 forever.
> 
>     Even if somebody takes care of backporting all needed changes (and this
>     doesn't become too expensive due to the code diverging between master
>     and 18.0) and none are missed, there's a good chance it won't work at
>     any given time, due to the delay between the changes landing in master
>     and 18.0.
> 
> 
> master might not work at any given time either. You are basically
> admitting that supporting LLVM 7 in 18.0 is the same as master except
> for the small delay, which confirms what I said. :)

A fix for master is usually available the same day. And while occasional
breakage is acceptable for master, not so much for a stable branch. So
no, I don't see it being the same at all, not even close.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer