qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"libvir-list@redhat.com" <libvir-list@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"Aleksandar Markovic" <amarkovic@wavecomp.com>,
	"Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [libvirt] [PATCH-for-4.2] hw/mips: Deprecate the r4k machine
Date: Mon, 25 Nov 2019 15:40:21 +0000	[thread overview]
Message-ID: <20191125154021.GI4157473@redhat.com> (raw)
In-Reply-To: <CAL1e-=hktyuAzESyZMz3P4a9aq17dsrrzWpyXYfFYn=cWP3e4A@mail.gmail.com>

On Mon, Nov 25, 2019 at 03:45:35PM +0100, Aleksandar Markovic wrote:
> On Monday, November 25, 2019, Philippe Mathieu-Daudé <philmd@redhat.com>
> wrote:
> 
> > The r4k machine was introduced in 2005 (6af0bf9c7) and its last
> > logical change was in 2005 (9542611a6). After we can count 164
> > maintenance commits (QEMU API changes) with the exception of
> > 1 fix in 2015 (memory leak, commit 3ad9fd5a).
> >
> >
> Please don't start any deprecation process. This requires certain
> consultation within my company. Rest assured that everyone's opinion will
> be taken into account while doing consiltation.

The idea of having a deprecation process is precisely to
allow time for people like to provide feedback before any
deletion takes place. So this is not a reason to delay
starting of deprecation.

The process lasts for 2 releases before we delete anything:

  https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features

When we start the clock now, it is deprecated when 5.0 releases
in April 2020, and still deprecated with 5.1 in August 2020.

The code won't be deleted until Sep 2020 when 5.2 dev cycle opens,
and there's still time to undelete it right up until the 5.2 feature
freeze in late Oct 2020. That's 11 months away, which is plenty of
time for feedback IMHO.

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 :|



  parent reply	other threads:[~2019-11-25 15:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 10:41 [PATCH-for-4.2] hw/mips: Deprecate the r4k machine Philippe Mathieu-Daudé
2019-11-25 14:45 ` Aleksandar Markovic
2019-11-25 14:56   ` Philippe Mathieu-Daudé
2019-11-25 15:40   ` Daniel P. Berrangé [this message]
2019-11-25 15:48     ` [libvirt] " Eric Blake
2019-11-27 19:40     ` Aleksandar Markovic
2019-11-27 21:12       ` Philippe Mathieu-Daudé
2019-11-25 15:23 ` Aurelien Jarno
2019-11-26 20:46 ` Aleksandar Markovic
2019-11-26 21:15   ` Philippe Mathieu-Daudé
2019-11-26 22:03     ` Aleksandar Markovic
2019-11-26 22:11       ` Philippe Mathieu-Daudé
2019-11-27 18:46 ` Aleksandar Markovic
2019-11-27 18:47 ` Aleksandar Markovic
2019-11-27 21:17   ` Philippe Mathieu-Daudé
2019-11-27 21:30     ` Aleksandar Markovic
2019-11-27 21:31     ` Aleksandar Markovic
2019-11-27 22:35       ` Philippe Mathieu-Daudé
2019-12-17 18:10 ` Thomas Huth
2019-12-17 18:43   ` [EXTERNAL]Re: " Aleksandar Markovic
2020-09-04 16:57     ` Philippe Mathieu-Daudé
2020-09-10  7:36       ` Philippe Mathieu-Daudé

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=20191125154021.GI4157473@redhat.com \
    --to=berrange@redhat.com \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=aleksandar.rikalo@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=hpoussin@reactos.org \
    --cc=libvir-list@redhat.com \
    --cc=philmd@redhat.com \
    --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 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).