qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Publishing docs for formal releases
Date: Mon, 28 Sep 2020 14:49:58 +0100	[thread overview]
Message-ID: <20200928134958.GG2230076@redhat.com> (raw)

We currently have a cronjob publishing:

   https://www.qemu.org/docs/master/

The URL was chosen such that we would also publish docs for each release
at URLs like

   https://www.qemu.org/docs/5.0.0

The latter part has not happened yet.

IIUC, we first introduced the new docs approach in 4.0.0, so ideally we
would publish our historical docs for 4.0.0 releases onwards, including
each minor point release on stable branches. So this means 4.0.0, 4.0.1
4.1.0, 4.1.1, 4.2.0, 4.2.1, 5.0.0, 5.0.1 and 5.1.0.

What needs to happen to turn this into reality ? On IRC it was sugggested
that this be done as part of the release process handled by Michael Roth.

Is there anything blocking this ?

One we have docs publishing happening, then we'll want to also update

  https://www.qemu.org/documentation/

to link people to the docs for each release when making a release.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



                 reply	other threads:[~2020-09-28 13:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200928134958.GG2230076@redhat.com \
    --to=berrange@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).