On Sep 27, 2017, at 9:23 AM, Arjan van de Ven
On 9/27/2017 6:34 AM, Allen, Benjamin S. wrote:
> On Sep 27, 2017, at 8:27 AM, Arjan van de Ven <arjan(a)linux.intel.com> wrote:
>> On 9/27/2017 6:19 AM, Allen, Benjamin S. wrote:
>>> Appears the current release is linked to 17960, while a number of later
releases are available. 18010 being the latest. Is this intentional?
>> current generally is the latest release that passed QA.
>> you'll see newer things show up in releases/ and in the swupd
"staging" channel ahead of QA passing,
>> once a release passes QA, the current gets updated.
>> (staging channel is like a beta channel in chrome, you can use "swupd update
--format staging" to go to such a release)
> Is the release QA status available anywhere? Something analogous to a CI tool output
perhaps, showing what's failing?
it's not currently available, but if people want it we can look into this
It would be useful to see QA/build issues on a staged releases. For example I'm
testing 17990 with the Linux config changes I requested, but since it wasn't released
I don't know what else I'll be running into.
also it does not always mean QA failed; it can also mean QA has not
run yet, or the build process aborted halfway, say due to a file conflict between packages
(we never reuse numbers as a policy, we fix whatever broke and start with the next
number.... numbers are cheap)
Agreed numbers are cheap. Having a status, log, etc associated with staged non-released
releases makes things much more clear however.