From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Maintainer attn for 3.1 release changelog
Date: Thu, 1 Nov 2018 17:12:46 +0000 [thread overview]
Message-ID: <20181101171246.GK23712@redhat.com> (raw)
It is that time[1] of the release cycle when maintainers can make a start
on filling in the release changelog info for 3.1. I created the basic
page structure copying from 3.0 :
https://wiki.qemu.org/ChangeLog/3.1
Anyone who has sent a pull request in this dev cycle should fill in the
info about changes they sent.
Regards,
Daniel
[1] Maybe we should in fact create the changelog pages at the very start
of each release cycle.
When Peter sends a mail notifying that a pull request is merged, the
boilerplate email text could include a reminder & link to the latest
changelog page to be filled in.
--
|: 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 :|
next reply other threads:[~2018-11-01 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 17:12 Daniel P. Berrangé [this message]
2018-11-01 17:27 ` [Qemu-devel] Maintainer attn for 3.1 release changelog Peter Maydell
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=20181101171246.GK23712@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.