8:51 a.m.
It's time to get a new release out. Simplest would be to enter freeze
tomorrow, then we can plan an RC2 by Friday, and if everything looks
good have the release on time next Monday.
Hope this works for everybody,
thanks,
Daniel
--
Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
5:35 a.m.
On 3/26/19 8:51 AM, Daniel Veillard wrote:
It's time to get a new release out. Simplest would be to enter
freeze
tomorrow, then we can plan an RC2 by Friday, and if everything looks
good have the release on time next Monday.
Not sure what time you are planning on starting the freeze, but my
series for incremental backups (v7 just posted) might be ready to get in
the 5.2 release.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
7:39 a.m.
On Wed, Mar 27, 2019 at 05:35:12AM -0500, Eric Blake wrote:
On 3/26/19 8:51 AM, Daniel Veillard wrote:
> It's time to get a new release out. Simplest would be to enter freeze
> tomorrow, then we can plan an RC2 by Friday, and if everything looks
> good have the release on time next Monday.
Not sure what time you are planning on starting the freeze, but my
series for incremental backups (v7 just posted) might be ready to get in
the 5.2 release.
Sorry I cut it this morning my time. If as I assume it's a new functionality
and unlikely to introduce regressions then maybe you can sneak it before RC2
today or tomorrow. If the impact is wide on the other hand, maybe it's safer
to wait until Tuesday to push it.
Makes sense ?
Daniel
--
Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
9:05 a.m.
On Thu, Mar 28, 2019 at 01:39:14PM +0100, Daniel Veillard wrote:
On Wed, Mar 27, 2019 at 05:35:12AM -0500, Eric Blake wrote:
> On 3/26/19 8:51 AM, Daniel Veillard wrote:
> > It's time to get a new release out. Simplest would be to enter freeze
> > tomorrow, then we can plan an RC2 by Friday, and if everything looks
> > good have the release on time next Monday.
>
> Not sure what time you are planning on starting the freeze, but my
> series for incremental backups (v7 just posted) might be ready to get in
> the 5.2 release.
Sorry I cut it this morning my time. If as I assume it's a new functionality
and unlikely to introduce regressions then maybe you can sneak it before RC2
today or tomorrow. If the impact is wide on the other hand, maybe it's safer
to wait until Tuesday to push it.
Makes sense ?
I already posted in the patch review thread saying we should *not* merge
this.
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 :|
2066
days inactive
2068
days old
3 comments
3 participants
participants (3)
-
Daniel P. Berrangé -
Daniel Veillard -
Eric Blake