All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>,
	YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] ref-manual: move release notes to separate document
Date: Mon, 14 Jun 2021 15:39:33 +0200	[thread overview]
Message-ID: <44a668f4-5923-bddc-992f-69c00bfb8f1c@bootlin.com> (raw)
In-Reply-To: <20210614081021.zoh3ph7mgtjuui5u@qschulz>

Hi Quentin,

On 6/14/21 10:10 AM, Quentin Schulz wrote:
> I was wondering if it made more sense to pick more expressive words for
> "current" and "previous" release manuals. Something like
> maintained/unmaintained for example? Or... EOL/outdated for the second
> kind?


Very idea. It always sounded strange to me. I could propose "maintained"
(or supported?) and "outdated" (which is shorter than "unmaintained" for
use in the left menu).

>
> Also, I would move the release number after the release name, because
> it's the place where you usually have section number in e.g. Reference
> Manual in the navigation panel.


Indeed, for the same reason, I had to prefix the title of migration
guides by "Release" to avoid this confusion.
A benefit of doing this is that we would be more consistent withe the
way the migration guides are listed.

I'll submit the two changes that you proposed.

Thanks again :-)

Michael.

-- 

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


      reply	other threads:[~2021-06-14 13:39 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
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 [this message]

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=44a668f4-5923-bddc-992f-69c00bfb8f1c@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=nicolas.dechesne@linaro.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=richard.purdie@linuxfoundation.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.