All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] docs: simplify and clarify the platform support rules
Date: Thu, 17 Sep 2020 17:34:13 +0100	[thread overview]
Message-ID: <20200917163413.GM1597829@redhat.com> (raw)
In-Reply-To: <20200917162851.GP7594@habkost.net>

On Thu, Sep 17, 2020 at 12:28:51PM -0400, Eduardo Habkost wrote:
> On Thu, Sep 17, 2020 at 04:56:06PM +0100, Daniel P. Berrangé wrote:
> > The distinction between short life and long life Linux distributions
> > turned out to be redundant. They can both be covered in a simple way
> > by noting support will target the current release, and the previous
> > release for a period of two years or until its EOL. This rule can also
> > apply to the other UNIX based distros, leaving only Windows needing a
> > different set of rules.
> > 
> > This also clarifies that Debian LTS is out of scope, because the LTS
> > support is provided by a separate group from the main Debian maintainer
> > team.
> > 
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > 
> > This is a spin off from the Python 3.5 thread
> > 
> > https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06358.html
> > 
> >  docs/system/build-platforms.rst | 59 ++++++++++-----------------------
> >  1 file changed, 18 insertions(+), 41 deletions(-)
> > 
> > diff --git a/docs/system/build-platforms.rst b/docs/system/build-platforms.rst
> > index 9734eba2f1..03d2fd217f 100644
> > --- a/docs/system/build-platforms.rst
> > +++ b/docs/system/build-platforms.rst
> > @@ -29,51 +29,28 @@ The Repology site https://repology.org is a useful resource to identify
> [...]
> > +Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
> > +-----------------------------------------
> [...]
> > +For FreeBSD, decisions will be made based on the contents of the ports tree;
> > +for macOS, `HomeBrew`_ will be used, although `MacPorts`_ is expected to carry
> > +similar versions.
> 
> Shouldn't we mention NetBSD and OpenBSD too?

Hmm, yes, i updated the section heading but not the text

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-17 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 15:56 [PATCH] docs: simplify and clarify the platform support rules Daniel P. Berrangé
2020-09-17 16:03 ` no-reply
2020-09-17 16:15 ` Thomas Huth
2020-09-17 16:24 ` no-reply
2020-09-17 16:28 ` Eduardo Habkost
2020-09-17 16:34   ` Daniel P. Berrangé [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=20200917163413.GM1597829@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 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.