All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] ref-manual: move release notes to separate document
Date: Fri, 11 Jun 2021 10:15:36 +0100	[thread overview]
Message-ID: <59c947fa6fc26b984a54b9b781367e41360a713b.camel@linuxfoundation.org> (raw)
In-Reply-To: <63f24dc7-4fbf-6543-6e1d-8eadfe3cd338@bootlin.com>

On Fri, 2021-06-11 at 09:48 +0200, Michael Opdenacker wrote:
> Hello,
> 
> On 6/10/21 2:03 PM, Michael Opdenacker wrote:
> > Hi Nicolas,
> > 
> > On 6/10/21 12:04 PM, Nicolas Dechesne wrote:
> > > Can you please push to master-next , so that everyone can see what it
> > > looks like without having to rebuild
> > > (e.g. http://docs.yoctoproject.org/next/
> > > <http://docs.yoctoproject.org/next/> will be updated after you push)? 
> > > 
> > > e.g. i am cc'ding Vineela (release manager) , so that she gets a
> > > chance to review.
> > 
> > Done. I couldn't find this URL any more, so I wasn't sure that the
> > functionality existed.
> > 
> > Thanks in advance for the reviews,
> 
> 
> With these changes visible on http://docs.yoctoproject.org/next/, the
> location of the release notes is changing. How much would this break
> other resources, such as links on our website? I remember Paul's warning
> 5 days before Hardknott was released, but I hope we are now far enough
> from the next release.
> 
> Another question is whether "Release notes" is the right title for these
> migration guides, at least in the left menu. Shouldn't we just call them
> "Release migration guides" as they truly are, knowing that the true
> release notes are on
> https://www.yoctoproject.org/software-overview/downloads/?

Yes, they're migration guides, the release notes are something different.

Cheers,

Richard


  reply	other threads:[~2021-06-11  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1675A932C413C877.8243@lists.yoctoproject.org>
2021-06-10  9:35 ` [PATCH] ref-manual: move release notes to separate document Michael Opdenacker
     [not found] ` <16872EDF3FBC0621.15202@lists.yoctoproject.org>
2021-06-10  9:39   ` [docs] " Michael Opdenacker
2021-06-10 10:04     ` Nicolas Dechesne
2021-06-10 12:03       ` Michael Opdenacker
     [not found]       ` <168736F45421387B.20336@lists.yoctoproject.org>
2021-06-11  7:48         ` Michael Opdenacker
2021-06-11  9:15           ` Richard Purdie [this message]
2021-06-11  9:52             ` Nicolas Dechesne
2021-06-11 16:37               ` Michael Opdenacker
2021-06-11 10:13             ` Michael Opdenacker
2021-06-11 17:24               ` Quentin Schulz
2021-06-11 18:04                 ` Michael Opdenacker
     [not found]                 ` <16879940C9237AEB.32248@lists.yoctoproject.org>
2021-06-14  8:05                   ` Michael Opdenacker
2021-06-14  8:10                     ` Quentin Schulz
2021-06-14 13:39                       ` 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=59c947fa6fc26b984a54b9b781367e41360a713b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=vineela.tummalapalli@intel.com \
    /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.