All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] [honister] conf: update for release 3.4
Date: Wed, 27 Oct 2021 13:28:37 +0200	[thread overview]
Message-ID: <20211027112837.7oaibv2saa4ak2gn@fedora> (raw)
In-Reply-To: <20211027105243.7ncoejzfms6rcxyh@fedora>

Hi all,

Just to make sure the discussion does not get mistaken as an agreement
on this patch being dropped, can we still merge this one patch in honister
branch please :) ? It still applies even though we missed the release tag.

Cheers,
Quentin

On Wed, Oct 27, 2021 at 12:52:43PM +0200, Quentin Schulz wrote:
> Hi Richard,
> 
> On Wed, Oct 27, 2021 at 11:45:35AM +0100, Richard Purdie wrote:
> > On Wed, 2021-10-27 at 12:40 +0200, Quentin Schulz wrote:
> > > I specifically sent this patch before we tagged the release to be sure
> > > we don't have the same issue as on 3.3. But we do have the same issue
> > > now that yocto-3.4 is tagged and this patch is not in...
> > 
> > Sorry, too many different moving pieces to track with release :(
> > 
> > Whilst it was sent before tagging, the release was already in QA and the
> > revisions used in QA are used in the final release tags as if we don't that
> > causes a different set of problems/concerns.
> > 
> 
> It's alright, just a bit sad that we could have done things better for
> this release and missed the opportunity.
> 
> This however highlights an issue in the release process for the documentation.
> Let's make sure we lower the probability of this issue to happen again
> in next releases.
> I guess it'd make sense to work on some helper script for releases/branch
> maintainers so we don't forget some bits? I'll try to come up with
> something :)
> 
> > > Can we settle on a solution? I assume moving git tags is deemed to risky
> > > which I can agree with but the issue(s) need to be resolved. Can we
> > > patch the tagged release from within yocto-autobuilder-helper doc-building
> > > process?
> > 
> > To clear this up for now I will take patching in the doc building process with a
> > patch or sed command.
> > 
> 
> I'll prepare a patch for patchng the release in the
> yocto-autobuilder-helper doc-building process and send that ASAP. If not
> sent by the end of the week, please scream at me.
> 
> Cheers,
> Quentin

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#2050): https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_g_docs_message_2050&d=DwIFaQ&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=U9q4K1YP08t9YtMVLPvDSS7TzYccgrrgJEMZs1MryCBQci7jrUIj7ztk7n19OOzo&s=Adx6-VwSObnDF3Q2C6RCQ_ww8XahPVCDYPZSS4mzBI4&e= 
> Mute This Topic: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_mt_86485182_6293953&d=DwIFaQ&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=U9q4K1YP08t9YtMVLPvDSS7TzYccgrrgJEMZs1MryCBQci7jrUIj7ztk7n19OOzo&s=BNdewZgB9JAQpu7SroEKuJbb4l1M8DVthR6VrgxRE0M&e= 
> Group Owner: docs+owner@lists.yoctoproject.org
> Unsubscribe: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_g_docs_unsub&d=DwIFaQ&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=U9q4K1YP08t9YtMVLPvDSS7TzYccgrrgJEMZs1MryCBQci7jrUIj7ztk7n19OOzo&s=memvkvhhp_x3w4x-O1Aa5JLafiJEl57xGj2aPD_obnU&e=  [quentin.schulz@theobroma-systems.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  reply	other threads:[~2021-10-27 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  8:43 [PATCH] [honister] conf: update for release 3.4 Quentin Schulz
2021-10-27 10:40 ` Quentin Schulz
2021-10-27 10:45   ` [docs] " Richard Purdie
2021-10-27 10:52     ` Quentin Schulz
2021-10-27 11:28       ` Quentin Schulz [this message]
2021-10-29 16:15         ` Michael Opdenacker
2021-10-29 17:02           ` Quentin Schulz
2021-11-10 18:44             ` Quentin Schulz

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=20211027112837.7oaibv2saa4ak2gn@fedora \
    --to=quentin.schulz@theobroma-systems.com \
    --cc=docs@lists.yoctoproject.org \
    --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.