All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [yocto-docs][dunfell 1/3] ref-system-requirements.rst: Add Debian 11 to list of supported distros
Date: Wed, 10 Nov 2021 08:50:22 -1000	[thread overview]
Message-ID: <CAOSpxdYQE9eqcwAFUnoNWx6RgWL3V1PBUDJ5xFM7iHMoxrymEg@mail.gmail.com> (raw)
In-Reply-To: <1fad7cb1-bb18-b633-7bfb-9a0f7c16ca4d@bootlin.com>

On Wed, Nov 10, 2021 at 8:42 AM Michael Opdenacker
<michael.opdenacker@bootlin.com> wrote:
>
>
> On 11/10/21 6:53 PM, Steve Sakoman wrote:
> > On Wed, Nov 10, 2021 at 7:47 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Wed, 2021-11-10 at 18:44 +0100, Michael Opdenacker wrote:
> >>> Hi Steve,
> >>>
> >>> On 11/10/21 6:08 PM, Steve Sakoman wrote:
> >>>> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> >>>> ---
> >>>>  documentation/ref-manual/ref-system-requirements.rst | 2 ++
> >>>>  1 file changed, 2 insertions(+)
> >>>>
> >>>> diff --git a/documentation/ref-manual/ref-system-requirements.rst b/documentation/ref-manual/ref-system-requirements.rst
> >>>> index d238dc454..4c4a7cf0a 100644
> >>>> --- a/documentation/ref-manual/ref-system-requirements.rst
> >>>> +++ b/documentation/ref-manual/ref-system-requirements.rst
> >>>> @@ -65,6 +65,8 @@ distributions:
> >>>>
> >>>>  -  Debian GNU/Linux 10.x (Buster)
> >>>>
> >>>> +-  Debian GNU/Linux 11.x (Bullseye)
> >>>
> >>> Great!
> >>> Could we apply these to "master"  too?
> >> We should only be applying things to older branches which are resolved in master
> >> one way or another too. And yes, the autobuilder has debian11 workers so this
> >> should go to master as well.
> > My bad, I assumed that master already had this change since the debian
> > 11 workers have been around for a while :-(
>
>
> No problem. This helps me to understand the process.
> Does it apply to Fedora 34 too? Is it enough to see a few successful
> runs on https://autobuilder.yoctoproject.org/typhoon/#/builders/86 to
> assume that Fedora 34 is supported?

Fedora 34 workers have been around for some time now too, so it should
be fine for master.

For dunfell I first make sure that oe-selftest and reproducible
succeed on the new worker, then wait for several weeks of normal
builds with the new worker enabled (by using my contrib/sakoman
autobuilder helper branch)

If all goes well I submit the patch for autobuilder2 to enable those
workers for the dunfell autobuilder helper branch, and finally when
that is in I submit the patches to meta-yocto and yocto-docs to add
the distros.

Steve

>
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>


  reply	other threads:[~2021-11-10 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 17:08 [yocto-docs][dunfell 0/3] Patch review Steve Sakoman
2021-11-10 17:08 ` [yocto-docs][dunfell 1/3] ref-system-requirements.rst: Add Debian 11 to list of supported distros Steve Sakoman
     [not found]   ` <70b01de2-15cc-225e-9d47-95ddfc363ba0@bootlin.com>
     [not found]     ` <2ef59077f06541a8f71d8b644a4e997fadc088aa.camel@linuxfoundation.org>
2021-11-10 17:53       ` [docs] " Steve Sakoman
2021-11-10 18:42         ` Michael Opdenacker
2021-11-10 18:50           ` Steve Sakoman [this message]
2021-11-10 17:08 ` [yocto-docs][dunfell 2/3] ref-system-requirements.rst: Add Fedora 34 " Steve Sakoman
2021-11-10 17:08 ` [yocto-docs][dunfell 3/3] documentation: prepare for 3.1.12 release Steve Sakoman
2021-11-11  4:08   ` [docs] " Mittal, Anuj
2021-11-11  4:11     ` Steve Sakoman
2021-11-12 11:06 ` [docs] [yocto-docs][dunfell 0/3] Patch review Michael Opdenacker

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=CAOSpxdYQE9eqcwAFUnoNWx6RgWL3V1PBUDJ5xFM7iHMoxrymEg@mail.gmail.com \
    --to=steve@sakoman.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.