From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] 4.0 changelog open - maintainers update after PULL is merged
Date: Wed, 12 Dec 2018 11:09:19 +0000 [thread overview]
Message-ID: <20181212110919.GB31033@redhat.com> (raw)
Rather than wait until the feature freeze to fill out the release changelog,
lets try a new approach for 4.0 where we fill it out as code is merged.
I've created a changelog template for 4.0:
https://wiki.qemu.org/ChangeLog/4.0
Any maintainer who sends a PULL request, should make appropriate additions
to the changelog once their PULL is merged by Peter, if it had any changes
users need to be aware of.
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:[~2018-12-12 11:09 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=20181212110919.GB31033@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.