Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Aug 01 I suggest entering the freeze on Wednesday Jul 26 and tagging RC2 on Friday Jul 28. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jul 03 I suggest entering the freeze on Tuesday Jun 27 and tagging RC2 on Friday Jun 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jun 01 I suggest entering the freeze on Friday May 26 and tagging RC2 on Tuesday May 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on May 02 I suggest entering the freeze on Tuesday Apr 25 and tagging RC2 on Thursday Apr 27. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Mar 31 (in the evening since Apr 1 is Saturday) I suggest entering the freeze on Monday Mar 27 and tagging RC2 on Wednesday Mar 29 in the afternoon. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Mar 01 I suggest entering the freeze on Wednesday Feb 22 and tagging RC2 on Monday Feb 27. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jan 16 I suggest entering the freeze on Tuesday Jan 10 and tagging RC2 on Thursday Jan 12. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the last release of libvirt in 2022. To aim for the release on Dec 01 I suggest entering the freeze on Thursday Nov 24 and tagging RC2 on Tuesday Nov 29. I hope this works for everyone. Jirka
Re: Plans for the next release
On Wed, Oct 19, 2022 at 14:59:42 +0200, Jiri Denemark wrote: > We are getting close to the next release of libvirt. To aim for the > release on Nov 01 I suggest entering the freeze on Friday Oct 28 and > tagging RC2 on Tuesday Oct 25. Oops, RC2 should be on Oct 28 and RC1, i.e., entering freeze on Oct 25. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Nov 01 I suggest entering the freeze on Friday Oct 28 and tagging RC2 on Tuesday Oct 25. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Oct 03 I suggest entering the freeze on Tuesday Sep 27 and tagging RC2 on Friday Sep 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Sep 01 I suggest entering the freeze on Friday Aug 26 and tagging RC2 on Tuesday Aug 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Aug 01 I suggest entering the freeze on Tuesday Jul 26 and tagging RC2 on Friday Jul 29. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jul 01 I suggest entering the freeze on Monday Jun 27 and tagging RC2 on Wednesday Jun 29. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on June 01 I suggest entering the freeze on Wednesday May 25 in the evening and tagging RC2 on Monday May 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on May 02 I suggest entering the freeze on Tuesday Apr 26 and tagging RC2 on Friday Apr 29. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the April Fools' release on Apr 01 I suggest entering the freeze on Monday Mar 28 and tagging RC2 on Wednesday Mar 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Mar 01 I suggest entering the freeze on Wednesday Feb 23 and tagging RC2 on Friday Feb 25. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jan 14 I suggest entering the freeze on Monday Jan 10 and tagging RC2 on Wednesday Jan 12. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Dec 01 I suggest entering the freeze on Thursday Nov 25 and tagging RC2 on Monday Nov 29. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Nov 01 I suggest entering the freeze on Tuesday Oct 26 and tagging RC2 on Friday Oct 29. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Oct 01 I suggest entering the freeze on Monday Sep 27 and tagging RC2 on Wednesday Sep 29. I hope this works for everyone. Jirka
Plans for the next release
I'm sending this early as I'll be out until Aug 25, but don't worry I'll be back in time to handle the whole release process. To aim for the release on Sep 01 I suggest entering the freeze on Thursday Aug 26 and tagging RC2 on Monday Aug 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Aug 02 I suggest entering the freeze on Tuesday Jul 27 and tagging RC2 on Thursday Jul 29. I'll be on PTO next week and thus I won't be able to make the RC releases, Pavel Hrdina volunteered to make them while I'm away. This means RC1 and RC2 releases won't be signed by my PGP key, but it shouldn't be a big deal as the final release is what matters and I will be back in time to handle it myself. Thanks Pavel for backing me up. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jul 01 I suggest entering the freeze on Friday Jun 25 and tagging RC2 on Tuesday Jun 29. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Jun 01 I suggest entering the freeze on Tuesday May 25 and tagging RC2 on Thursday May 27. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on May 03 I suggest entering the freeze on Tuesday Apr 27 and tagging RC2 on Thursday Apr 29 in the afternoon. I hope this works for everyone. Jirka
Re: Plans for the next release
On Fri, Mar 19, 2021 at 10:29:44 +0100, Jiri Denemark wrote: > We are getting close to the next release of libvirt. To aim for the > release on Apr 01 I suggest entering the freeze on Froday Mar 26 and > tagging RC2 on Tuesday Mar 30. Since this is the last libvirt release before qemu-6.0 gets released [1], we must include the series for adapting to '-object' qapification [2]. This is needed as it adapts to the removal of the 'props' sub-property [3] which we still use currently [4]. [1] https://wiki.qemu.org/Planning/6.0 [2] https://listman.redhat.com/archives/libvir-list/2021-March/msg01049.html [3] https://gitlab.com/qemu-project/qemu/-/commit/50243407457a9fb0ed17b9a9ba9fc9aee09495b1 [4] https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_monitor.c#L3025
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Apr 01 I suggest entering the freeze on Froday Mar 26 and tagging RC2 on Tuesday Mar 30. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Mar 01 I suggest entering the freeze on Monday Feb 22 and tagging RC2 on Thursday Feb 25. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the first release of libvirt in 2021. To aim for the release on Jan 15 I suggest entering the freeze on Friday Jan 08 in the evening or during the weekend and tagging RC2 on Wednesday Jan 13. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the last release of libvirt in 2020. To aim for the release on Dec 01 I suggest entering the freeze on Wednesday Nov 25 and tagging RC2 on Friday Nov 27. I hope this works for everyone. Jirka
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Nov 02 I suggest entering the freeze on Monday Oct 26 and tagging RC2 on Thursday Oct 29. I hope this works for everyone. Jirka
Re: Plans for the next release
On Mon, Sep 21, 2020 at 14:38:55 +0200, Ján Tomko wrote: > [please don't top-post on technical mailing lists] > > On a Monday in 2020, Alexander Wels wrote: > >Which version would that be? 6.7.0? > > > > No, 6.7.0 is already out: > https://www.redhat.com/archives/libvirt-announce/2020-September/msg0.html > > The next release is 6.8.0 > > Since 2.0.0 we follow a time-based versioning scheme: > https://libvirt.org/downloads.html#numbering And if you are not sure, you can always check meson.build, which contains the upcoming release (it is incremented immediately after each release). Jirka
Re: Plans for the next release
[please don't top-post on technical mailing lists] On a Monday in 2020, Alexander Wels wrote: Which version would that be? 6.7.0? No, 6.7.0 is already out: https://www.redhat.com/archives/libvirt-announce/2020-September/msg0.html The next release is 6.8.0 Since 2.0.0 we follow a time-based versioning scheme: https://libvirt.org/downloads.html#numbering Jano signature.asc Description: PGP signature
Re: Plans for the next release
Which version would that be? 6.7.0? On Mon, Sep 21, 2020 at 3:16 AM Jiri Denemark wrote: > We are getting close to the next release of libvirt. To aim for the > release on Oct 01 I suggest entering the freeze on Thursday Sep 24 and > tagging RC2 on Tuesday Sep 29. > > I hope this works for everyone. > > Jirka > >
Plans for the next release
We are getting close to the next release of libvirt. To aim for the release on Oct 01 I suggest entering the freeze on Thursday Sep 24 and tagging RC2 on Tuesday Sep 29. I hope this works for everyone. Jirka
Plans for the next release
I'm sending this quite early this month as I'm on vacation tomorrow and next week and I wanted to make sure the plan for the release is advertised earlier than just a day or two before the freeze. To aim for the release on Sep 01 I suggest entering the freeze in two weeks on Wednesday Aug 26 and tagging RC2 on Friday Aug 28 in the afternoon. I hope this works for everyone. Jirka
Plans for the next release
Hi all, We are getting close to the next release of libvirt. Because I am on vacation next week, I think we will have a little bit longer freeze period (although mainly extended by a weekend). So to aim for the release at the beginning of August I suggest entering the freeze just before the upcoming weekend starts, i.e., on Friday July 24 (in late evening) and I think we can skip RC2 this time and just push the release on August 1 or 2. Normal freeze period would start on Monday with RC2 on Thursday and a final release on August 1, which is pretty similar in terms of frozen work days. I hope this works for everyone. Jirka
Re: [libvirt] ANNOUNCE: Plans for the next release
On Wed, May 16, 2018 at 01:38:06PM +0200, Pavel Hrdina wrote: > On Wed, May 16, 2018 at 12:09:15PM +0100, Daniel P. Berrangé wrote: > > On Mon, May 14, 2018 at 05:15:59PM +0200, Pavel Hrdina wrote: > > > Hi, > > > > > > I would like to make the next libvirt-dbus release with stable APIs, > > > there is a lot of them already implemented and other projects can start > > > adapting to use libvirt-dbus. > > > > > > The release version would be 1.0.0 and currently libvirt-dbus will > > > cover APIs up to libvirt-3.0.0 as a start point because that libvirt > > > version is available in all downstream distributions currently > > > supported by libvirt. > > > > > > So I would like to ask everyone to look at the APIs to check whether it > > > make sense and whether something is missing or could be excluded. > > > > I'd suggest writing a test that parses libvirt-api.xml and validates that > > your binary (or source code) contains a reference to each API, so that you > > know you have full coverage, and also so that CI builds when when new APIs > > are added to libvirt alerting you to close the gap. Just blacklist the > > APIs you don't want to expose. There's examples of such a test in the > > python, perl and go binding repos. > > Yes, definitely good suggestion. Actually I have it in my mind to do > it, but I was waiting until we implement all APIs. But since you've > mentioned it I've realized that it could be useful to do it now to in > order to track what APIs are left to implement so we don't miss any. Yeah, when I was writing the Go bindings, I created the test first, and blacklisted all missing APIs. Then gradually removed APIs from the blacklist as I implemented them, until I got just the bits I didn't want to expose. 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 :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] ANNOUNCE: Plans for the next release
On Wed, May 16, 2018 at 12:09:15PM +0100, Daniel P. Berrangé wrote: > On Mon, May 14, 2018 at 05:15:59PM +0200, Pavel Hrdina wrote: > > Hi, > > > > I would like to make the next libvirt-dbus release with stable APIs, > > there is a lot of them already implemented and other projects can start > > adapting to use libvirt-dbus. > > > > The release version would be 1.0.0 and currently libvirt-dbus will > > cover APIs up to libvirt-3.0.0 as a start point because that libvirt > > version is available in all downstream distributions currently > > supported by libvirt. > > > > So I would like to ask everyone to look at the APIs to check whether it > > make sense and whether something is missing or could be excluded. > > I'd suggest writing a test that parses libvirt-api.xml and validates that > your binary (or source code) contains a reference to each API, so that you > know you have full coverage, and also so that CI builds when when new APIs > are added to libvirt alerting you to close the gap. Just blacklist the > APIs you don't want to expose. There's examples of such a test in the > python, perl and go binding repos. Yes, definitely good suggestion. Actually I have it in my mind to do it, but I was waiting until we implement all APIs. But since you've mentioned it I've realized that it could be useful to do it now to in order to track what APIs are left to implement so we don't miss any. I'll look into it later, I guess there is no rush to do it before the release. Thanks, Pavel signature.asc Description: PGP signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] ANNOUNCE: Plans for the next release
On Mon, May 14, 2018 at 05:15:59PM +0200, Pavel Hrdina wrote: > Hi, > > I would like to make the next libvirt-dbus release with stable APIs, > there is a lot of them already implemented and other projects can start > adapting to use libvirt-dbus. > > The release version would be 1.0.0 and currently libvirt-dbus will > cover APIs up to libvirt-3.0.0 as a start point because that libvirt > version is available in all downstream distributions currently > supported by libvirt. > > So I would like to ask everyone to look at the APIs to check whether it > make sense and whether something is missing or could be excluded. I'd suggest writing a test that parses libvirt-api.xml and validates that your binary (or source code) contains a reference to each API, so that you know you have full coverage, and also so that CI builds when when new APIs are added to libvirt alerting you to close the gap. Just blacklist the APIs you don't want to expose. There's examples of such a test in the python, perl and go binding repos. > The idea of libvirt-dbus is not to export every API if there is a better > API to do the job, so for example: > > - all APIs that have both versions with and without flags we will > export only the one with flags. > > - some of the Stats APIs can be omitted since the same values are > also exported in the GetStats (virDomainListGetStats) > > I would like to make the release this week so any help or suggestion is > welcome. The API definition is in the data/org.libvirt.*.xml files. > -- > libvir-list mailing list > libvir-list@redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list 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 :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] ANNOUNCE: Plans for the next release
Hi, I would like to make the next libvirt-dbus release with stable APIs, there is a lot of them already implemented and other projects can start adapting to use libvirt-dbus. The release version would be 1.0.0 and currently libvirt-dbus will cover APIs up to libvirt-3.0.0 as a start point because that libvirt version is available in all downstream distributions currently supported by libvirt. So I would like to ask everyone to look at the APIs to check whether it make sense and whether something is missing or could be excluded. The idea of libvirt-dbus is not to export every API if there is a better API to do the job, so for example: - all APIs that have both versions with and without flags we will export only the one with flags. - some of the Stats APIs can be omitted since the same values are also exported in the GetStats (virDomainListGetStats) I would like to make the release this week so any help or suggestion is welcome. The API definition is in the data/org.libvirt.*.xml files. Thanks and regards Pavel signature.asc Description: PGP signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
