From berrange at redhat.com  Thu Jul 16 12:07:00 2020
From: berrange at redhat.com (Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?=)
Date: Thu, 16 Jul 2020 13:07:00 +0100
Subject: Suggestion to close this list
Message-ID: <20200716120700.GP227735@redhat.com>

This list does not have a significant amount of traffic on it since we
switched to using merge requests.

 - A handful of patches mistakenly sent to the list instead of merge request
 - A couple of release announcements
 - A couple of design discussions


GitLab has the ability to attach release notices to a tag, and publicises
them as releases. You can see an example of that here:

   https://gitlab.com/virt-viewer/virt-viewer/-/releases

The source code links there are the auto-generated tarballs from  git,
but you have the option of  linking to otehr tarballs in the release notes
text.  I'd suggest this is sufficient for new releases

For design discussions, I think we can use GitLab issues.

So I'm inclined to say we should close this mailing list, as it is largely
just a trap that accidentally attracts people away from our preferred use
of GitLab.

We would not delete the list, simply configure it to reject any newly
posted mail with a short message pointing people to GitLab.

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



From fidencio at redhat.com  Mon Jul 20 06:49:48 2020
From: fidencio at redhat.com (=?UTF-8?Q?Fabiano_Fid=C3=AAncio?=)
Date: Mon, 20 Jul 2020 08:49:48 +0200
Subject: Suggestion to close this list
In-Reply-To: <20200716120700.GP227735@redhat.com>
References: <20200716120700.GP227735@redhat.com>
Message-ID: <CAAY6XsdsKX_JXFYraqbOP9ac7ZTVasd5B2Z2PhJxHCmav0XogQ@mail.gmail.com>

On Thu, Jul 16, 2020 at 2:08 PM Daniel P. Berrang? <berrange at redhat.com> wrote:
>
> This list does not have a significant amount of traffic on it since we
> switched to using merge requests.
>
>  - A handful of patches mistakenly sent to the list instead of merge request
>  - A couple of release announcements
>  - A couple of design discussions
>
>
> GitLab has the ability to attach release notices to a tag, and publicises
> them as releases. You can see an example of that here:
>
>    https://gitlab.com/virt-viewer/virt-viewer/-/releases
>
> The source code links there are the auto-generated tarballs from  git,
> but you have the option of  linking to otehr tarballs in the release notes
> text.  I'd suggest this is sufficient for new releases
>
> For design discussions, I think we can use GitLab issues.
>
> So I'm inclined to say we should close this mailing list, as it is largely
> just a trap that accidentally attracts people away from our preferred use
> of GitLab.
>
> We would not delete the list, simply configure it to reject any newly
> posted mail with a short message pointing people to GitLab.

+1.

Best Regards,
-- 
Fabiano Fid?ncio