public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: kuzetsa <kuzetsa@gmail.com>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] Gentoo Kernel meeting
Date: Thu, 5 Jul 2018 23:52:56 -0400	[thread overview]
Message-ID: <17a7d18a-e446-646c-d9f2-3aa8bf0f2eb1@gmail.com> (raw)
In-Reply-To: <CANWzcUrsZyTdVu21+M90uNG4amrr-TmaFH0PhEyAReTZt9ujrg@mail.gmail.com>

On 07/05/2018 07:03 AM, Alice Ferrazzi wrote:
> Sent from my phone. Please excuse my brevity.
> 
> On Thu, 5 Jul 2018, 19:51 M. J. Everitt, <m.j.everitt@iee.org> wrote:
> 

{ ~pruned~ }

>> I'd like to discuss the possibility of harmonising the bumping and
>> stabilisation process across the currently maintained source packages,
>> so that, in principle, whilst they may not be fully supported via
>> Security Team (we already have disclaimers for this), users choosing to
>> opt for, eg. ck-sources, would know that because 90% of the code-base
>> has been 'approved' via gentoo-sources (upstream + gentoo patches) that
>> any discrepancy due to failure could be quickly narrowed down to the
>> patchset, and the relevant maintainer can choose to pursue with their
>> specific upstream. The extent to which this is feasible can be debated,
>> but if we can establish a basic procedure that is, eg. automated,
>> perhaps individual maintainers will want to 'pitch in' if the effort
>> required is minimal enough.
>> The objective would be to create a obvious 'choice' of "known-good"ish
>> kernels that any user could choose from, whilst preserving maintainer
>> workflow separation, etc.
>>
> 
> not sure to have understand correctly.
> you want to stabilize also ck-sources?
> there is not only the new patchset but is also using different kernel
> eclass function.
> I think when we can do stabilization from the Gentoo kernel ci starting to
> stabilize also other sources would be a path to consider.
> 
> thanks,
> Alice
> 


I'd prefer waiting until QA / CI is solid before any
discussion to stabilize sys-kernel/ck-sources. I'm not
opposed per-se, but there's only so much testing I can do
on my own (this is why I need to know the QA / CI tools
are working well for several months I think). If there's
sufficient testing (to know when things are stable) then
sure, I think it might be okay to try for in 1st or 2nd
quarter 2019.

3rd quarter 2018 I'm still "spread thin", and my
availability is limited this weekend. In the meantime I'll
do what I can to familiarize myself with lava. I'll be
using my own infrastructure for testing, and hope to have
some practical experience and ideas by the end of July.

-- kuza



  reply	other threads:[~2018-07-06  3:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  5:16 [gentoo-kernel] Gentoo Kernel meeting Alice Ferrazzi
2018-07-05 10:50 ` M. J. Everitt
2018-07-05 11:03   ` Alice Ferrazzi
2018-07-06  3:52     ` kuzetsa [this message]
2018-07-07  1:14 ` Richard Yao
2018-07-07  6:11   ` Alice Ferrazzi
2018-07-18  0:27 ` [gentoo-kernel] " Alice Ferrazzi
2018-09-19 23:21 ` [gentoo-kernel] QA / CI improvement using stage3 images under qemu kuzetsa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17a7d18a-e446-646c-d9f2-3aa8bf0f2eb1@gmail.com \
    --to=kuzetsa@gmail.com \
    --cc=gentoo-kernel@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox