Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-27 Thread Adam Williamson
On Fri, 2019-09-27 at 08:50 -0700, Tom Stellard wrote: > > The LLVM update has the necessary karma now and all the gating tests > have passed. Should I push this to stable now and then push the mesa > update later or should we still try to combine the updates? You can push LLVM and then mesa,

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-27 Thread Pete Walter
27.09.2019, 16:51, "Tom Stellard" : > The LLVM update has the necessary karma now and all the gating tests > have passed. Should I push this to stable now and then push the mesa > update later or should we still try to combine the updates? Yes, go for it and push it to stable. I'll submit mesa to

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-27 Thread Martin Kolman
On Thu, 2019-09-26 at 13:21 -0700, Adam Williamson wrote: > On Thu, 2019-09-26 at 20:55 +0200, Hans de Goede wrote: > > Hi Tom, > > > > On 26-09-2019 20:47, Tom Stellard wrote: > > > On 09/26/2019 11:24 AM, Adam Williamson wrote: > > > > On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: > >

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-27 Thread Tom Stellard
On 09/26/2019 01:21 PM, Adam Williamson wrote: > On Thu, 2019-09-26 at 20:55 +0200, Hans de Goede wrote: >> Hi Tom, >> >> On 26-09-2019 20:47, Tom Stellard wrote: >>> On 09/26/2019 11:24 AM, Adam Williamson wrote: On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: > On 09/26/2019

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Adam Williamson
On Thu, 2019-09-26 at 20:55 +0200, Hans de Goede wrote: > Hi Tom, > > On 26-09-2019 20:47, Tom Stellard wrote: > > On 09/26/2019 11:24 AM, Adam Williamson wrote: > > > On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: > > > > On 09/26/2019 11:03 AM, Adam Williamson wrote: > > > > > We are

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Adam Williamson
On Thu, 2019-09-26 at 20:51 +0200, Hans de Goede wrote: > > OTOH we also want F31 to work with current hardware when it ships; > and llvm is kinda special in this regard, its main use in Fedora > is inside the graphics stack and mesa needs llvm9 to support the > AMD Radeon 5700 series cards which

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Hans de Goede
Hi Tom, On 26-09-2019 20:47, Tom Stellard wrote: On 09/26/2019 11:24 AM, Adam Williamson wrote: On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: On 09/26/2019 11:03 AM, Adam Williamson wrote: We are currently in the "Beta to Pre Release" phase of the release cycle. The updates policy

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Hans de Goede
Hi, On 26-09-2019 20:24, Adam Williamson wrote: On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: On 09/26/2019 11:03 AM, Adam Williamson wrote: We are currently in the "Beta to Pre Release" phase of the release cycle. The updates policy for this phase -

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Tom Stellard
On 09/26/2019 11:24 AM, Adam Williamson wrote: > On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: >> On 09/26/2019 11:03 AM, Adam Williamson wrote: >>> We are currently in the "Beta to Pre Release" phase of the release >>> cycle. The updates policy for this phase - >>>

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Adam Williamson
On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote: > On 09/26/2019 11:03 AM, Adam Williamson wrote: > > We are currently in the "Beta to Pre Release" phase of the release > > cycle. The updates policy for this phase - > > https://fedoraproject.org/wiki/Updates_Policy#Beta_to_Pre_Release - > >

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Adam Williamson
On Thu, 2019-09-26 at 20:13 +0200, Igor Gnatenko wrote: > Well, we have updated LLVM to next major version even before > mid-cycle. I didn't check exactly when this happened before, but note there is a significant difference between different parts of the cycle. There are different rules for the

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Tom Stellard
On 09/26/2019 11:03 AM, Adam Williamson wrote: > We are currently in the "Beta to Pre Release" phase of the release > cycle. The updates policy for this phase - > https://fedoraproject.org/wiki/Updates_Policy#Beta_to_Pre_Release - > says: > > "From this point onwards maintainers MUST[1]: > >

Re: Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Igor Gnatenko
Well, we have updated LLVM to next major version even before mid-cycle. Since it is important for graphics stack. Compatibility package was always created. On the other hand, it requires proper coordination with other package maintainers. tl;dr I think it is fine to do rebase before F31 Final,

Major update to LLVM appearing in F31 without any communication, appears to violate update policy

2019-09-26 Thread Adam Williamson
We are currently in the "Beta to Pre Release" phase of the release cycle. The updates policy for this phase - https://fedoraproject.org/wiki/Updates_Policy#Beta_to_Pre_Release - says: "From this point onwards maintainers MUST[1]: Avoid Major version updates, ABI breakage or API changes if