[libvirt] Plan for next release

[Daniel Veillard]

  So I plan to to enter freeze later today, that way we can have RC2 around
Wed and possibly a release on the 1st or this week-end.
  I expect a quiet week as a lot of the dev will be at KVM Forum

Daniel

-- 
Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  I'm afraid I'm a bit behind. I suggest to enter freeze tomorrow morning
then pushing rc2 on Thursday and if everything goes well push the GA
during the w.e., a bit late but not too late.

  I hope this works for everybody,

   thanks,

Daniel

-- 
Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] plan for next release

[Daniel Veillard]

On Mon, May 28, 2018 at 04:48:08PM +0200, Erik Skultety wrote:
> On Mon, May 28, 2018 at 10:15:22AM +0200, Erik Skultety wrote:
> > On Mon, May 28, 2018 at 10:01:06AM +0200, Daniel Veillard wrote:
> > >   Seems the end of the month is coming soon !
> > > I suggest to enter freeze tomorrow morningm with plan for an RC2 on 
> > > Thursday
> > > and a final release on the week-end,
> > >
> > >   Hope this works for everybody,
> > >
> > >  thanks !
> >
> > Hi,
> > would Wednesday and RC2 on Friday work too? I'm asking because there's the 
> > AMD
> > SEV patches (I'm reviewing it at the moment)  which introduce a new API and 
> > we
> > really should get this into this release, the patches look good so far, so I
> > don't expect more than a v7 with mostly nitpick being fixed...
> >
> > Thanks,
> > Erik
> 
> I'm sorry, but I have to retract my optimism on making this into 4.4.0, 
> because
> I suggested addition of one more API to get the SEV platform certificates as
> these can be up to 8K of base64 string which I agree with Dan shouldn't be
> exposed in domain capabilities XML. Therefore, you can proceed with your
> original plan on freezing tomorrow.

  Ok, thanks !

Daniel

-- 
Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] plan for next release

[Erik Skultety]

On Mon, May 28, 2018 at 10:15:22AM +0200, Erik Skultety wrote:
> On Mon, May 28, 2018 at 10:01:06AM +0200, Daniel Veillard wrote:
> >   Seems the end of the month is coming soon !
> > I suggest to enter freeze tomorrow morningm with plan for an RC2 on Thursday
> > and a final release on the week-end,
> >
> >   Hope this works for everybody,
> >
> >  thanks !
>
> Hi,
> would Wednesday and RC2 on Friday work too? I'm asking because there's the AMD
> SEV patches (I'm reviewing it at the moment)  which introduce a new API and we
> really should get this into this release, the patches look good so far, so I
> don't expect more than a v7 with mostly nitpick being fixed...
>
> Thanks,
> Erik

I'm sorry, but I have to retract my optimism on making this into 4.4.0, because
I suggested addition of one more API to get the SEV platform certificates as
these can be up to 8K of base64 string which I agree with Dan shouldn't be
exposed in domain capabilities XML. Therefore, you can proceed with your
original plan on freezing tomorrow.

Erik

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] plan for next release

[Erik Skultety]

On Mon, May 28, 2018 at 10:01:06AM +0200, Daniel Veillard wrote:
>   Seems the end of the month is coming soon !
> I suggest to enter freeze tomorrow morningm with plan for an RC2 on Thursday
> and a final release on the week-end,
>
>   Hope this works for everybody,
>
>  thanks !

Hi,
would Wednesday and RC2 on Friday work too? I'm asking because there's the AMD
SEV patches (I'm reviewing it at the moment)  which introduce a new API and we
really should get this into this release, the patches look good so far, so I
don't expect more than a v7 with mostly nitpick being fixed...

Thanks,
Erik

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] plan for next release

[Daniel Veillard]

  Seems the end of the month is coming soon !
I suggest to enter freeze tomorrow morningm with plan for an RC2 on Thursday
and a final release on the week-end,

  Hope this works for everybody,

 thanks !

Daniel

-- 
Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  So first release for the year comes with a renumbering, so 4.0.0 should
come soon, usually we target mid january, so I suggest to enter freeze tomorrow
get an RC2 on Monday and hence have the first release Wed next week.

  I hope this works for everyone,

   thanks


Daniel


-- 
Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Michal Privoznik]

On 27.03.2017 03:52, Laine Stump wrote:

On 03/24/2017 07:47 AM, Daniel Veillard wrote:

  Hi all,

 if we want to release around the end of the month, I think
we need to enter freeze on Monday end of day (for me europe)
to try to get the release around the next week-end.

   I assume that work for everyone, if not please tell :-)


Before you freeze, see if Erik Skultety is ready to push the mediated
device patches. I went through them today and they look fine except a
couple of small issues.

I also have the remainder of the series about fixing MAC address
saving/restoring for SRIOV network devices that only needs an ACK on one
patch - I'd like to get that pushed before you freeze too, so hopefully
Michal can look at the one patch (it's reading/writing json in a small
file based on his recommendation and example code).



I did look at it. In exchange, I have a small (almost trivial) patches 
of two that could use some review too:


https://www.redhat.com/archives/libvir-list/2017-March/msg01002.html

But those are bug fixes, so no rush to get them in before the freeze.

Michal

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Laine Stump]

On 03/24/2017 07:47 AM, Daniel Veillard wrote:
>   Hi all,
> 
>  if we want to release around the end of the month, I think
> we need to enter freeze on Monday end of day (for me europe)
> to try to get the release around the next week-end.
> 
>I assume that work for everyone, if not please tell :-)

Before you freeze, see if Erik Skultety is ready to push the mediated
device patches. I went through them today and they look fine except a
couple of small issues.

I also have the remainder of the series about fixing MAC address
saving/restoring for SRIOV network devices that only needs an ACK on one
patch - I'd like to get that pushed before you freeze too, so hopefully
Michal can look at the one patch (it's reading/writing json in a small
file based on his recommendation and example code).


--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  Hi all,

 if we want to release around the end of the month, I think
we need to enter freeze on Monday end of day (for me europe)
to try to get the release around the next week-end.

   I assume that work for everyone, if not please tell :-)

Daniel

-- 
Daniel Veillard  | Red Hat Developers Tools http://developer.redhat.com/
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release(s)

[Laine Stump]

On Dec 1, 2016 6:12 AM, "Andrea Bolognani"  wrote:
>
> On Mon, 2016-11-28 at 21:53 -0500, Laine Stump wrote:
> > P.S. to Andrea - I will write a NEWS file entry, but I guess that can
be
> > safely pushed after Daniel freezes :-)
>
> You better! ;)

Posted last night. I'm not sure if it's too verbose.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release(s)

[Andrea Bolognani]

On Mon, 2016-11-28 at 21:53 -0500, Laine Stump wrote:
[...]
> it was too late in 
> the day to have a discussion with him about his question here:
> 
> https://www.redhat.com/archives/libvir-list/2016-November/msg01204.html
> 
> He didn't give a NACK for putting that function in now (rather than 
> using stat() directly), but also didn't give an ACK.

I did neither ACK nor NACK because I was wondering if the
approach you took, which is completely fine as far as the
specific functionality you are implementing is concerned
(should have stressed this fact more in my reply), was the
best one going forward, and wanted to discuss that with you.

What I failed to take into account is the fact that *you*
were on your PTO and, by the time you got back, *I* would
be on mine :(

But I see Eric helpfully jumped in and provided more positive
feedback that, along with my lack of NACK, convinced you to
push. That's great! We can discuss about this more in due
time, but there was really no reason to leave this feature
out of the release for what is just an implementation detail.

[...]
> P.S. to Andrea - I will write a NEWS file entry, but I guess that can be 
> safely pushed after Daniel freezes :-)

You better! ;)

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release(s)

[Daniel Veillard]

  Planning the release before flying, i.e. before you can do anything
my bad I was late. Patches 1 and 2 can't seem to be able to introduce
regressions. The meat is really into patches 3 and 4. if you and others
feel confident about those 2 then have the series pushed between rc1
and rc2, that still gives a bit of time for testing. And in worse case if
this w.e. we still have an issue pending we can delay onto next week for
the final 2.5.0,

  so go with plan :-)

Daniel
  
On Mon, Nov 28, 2016 at 09:53:20PM -0500, Laine Stump wrote:
> On 11/28/2016 03:06 PM, Daniel Veillard wrote:
> >   I'm late  so I think that if we don't want to slip too much
> > the best would be to enter freeze tomorrow (Tuesday) then have RC2
> > around Thursday and a release over the week-end.
> 
> Are you saying you want to freeze tomorrow *morning* your time (ie. before
> they "mess  with" your internet), or tomorrow *afternoon* (when it will of
> course be working properly again)?
> 
> I had hoped to push the series "qemu: assign vfio devices to PCIe addresses
> when appropriate" for this release,
> 
> https://www.redhat.com/archives/libvir-list/2016-November/msg00964.html
> 
> but by the time I got back from the long Thanksgiving holiday and caught up
> enough with my email to get to Andrea's reviews, it was too late in the day
> to have a discussion with him about his question here:
> 
> https://www.redhat.com/archives/libvir-list/2016-November/msg01204.html
> 
> He didn't give a NACK for putting that function in now (rather than using
> stat() directly), but also didn't give an ACK. My opinion is in my response:
> 
> https://www.redhat.com/archives/libvir-list/2016-November/msg01402.html
> 
> in short, I would rather add the (simple) new function now to promote its
> use, anticipating that it will be expanded as necessary when it is used in
> more places.
> 
> As long as this is okay and that patch can be ACKed, I have the minor
> modifications for the other 3 patches ready to go and can push with a few
> moments' notice.
> 
> As usual, don't screw up your schedule just to accomodate me, but if you can
> try pinging me on IRC prior to freezing (just in case I'm awake and I've
> gotten a response about that patch and can push), that would be appreciated
> (do go ahead and freeze if I don't respond)
> 
> P.S. to Andrea - I will write a NEWS file entry, but I guess that can be
> safely pushed after Daniel freezes :-)
> 
> > 
> >   That said they are supposed to mess with my internet tomorrow morning
> > and I'm travelling till the end of the week, but the above plan should
> > be doable. Hope that's okay with everybody.
> > 
> >   Then usually December is a low productivity month, and Feb is short,
> > so it is tempting to do like for previous years i.e. release mid-january
> > and end of Feb, except the Jan release will be 3.0.0.
> > 
> > Works for everybody ?
> > 
> > Daniel
> > 

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release(s)

[Daniel P. Berrange]

On Mon, Nov 28, 2016 at 09:06:41PM +0100, Daniel Veillard wrote:
>  I'm late  so I think that if we don't want to slip too much
> the best would be to enter freeze tomorrow (Tuesday) then have RC2
> around Thursday and a release over the week-end.
> 
>  That said they are supposed to mess with my internet tomorrow morning
> and I'm travelling till the end of the week, but the above plan should
> be doable. Hope that's okay with everybody.
> 
>  Then usually December is a low productivity month, and Feb is short,
> so it is tempting to do like for previous years i.e. release mid-january
> and end of Feb, except the Jan release will be 3.0.0.
> 
>Works for everybody ?

Yes, that matches our documented release schedule :-)

"releases made once a month on the 1st of each month give or 
 take a few days. The only exception is at the start of the 
 year where there are two 6 weeks gaps (first release in the
 middle of Jan, then skip the Feb release), giving a total of
 11 releases a year."

http://libvirt.org/downloads.html#schedule


Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://entangle-photo.org   -o-http://search.cpan.org/~danberr/ :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release(s)

[Laine Stump]

On 11/28/2016 03:06 PM, Daniel Veillard wrote:

  I'm late  so I think that if we don't want to slip too much
the best would be to enter freeze tomorrow (Tuesday) then have RC2
around Thursday and a release over the week-end.


Are you saying you want to freeze tomorrow *morning* your time (ie. 
before they "mess  with" your internet), or tomorrow *afternoon* (when 
it will of course be working properly again)?


I had hoped to push the series "qemu: assign vfio devices to PCIe 
addresses when appropriate" for this release,


https://www.redhat.com/archives/libvir-list/2016-November/msg00964.html

but by the time I got back from the long Thanksgiving holiday and caught 
up enough with my email to get to Andrea's reviews, it was too late in 
the day to have a discussion with him about his question here:


https://www.redhat.com/archives/libvir-list/2016-November/msg01204.html

He didn't give a NACK for putting that function in now (rather than 
using stat() directly), but also didn't give an ACK. My opinion is in my 
response:


https://www.redhat.com/archives/libvir-list/2016-November/msg01402.html

in short, I would rather add the (simple) new function now to promote 
its use, anticipating that it will be expanded as necessary when it is 
used in more places.


As long as this is okay and that patch can be ACKed, I have the minor 
modifications for the other 3 patches ready to go and can push with a 
few moments' notice.


As usual, don't screw up your schedule just to accomodate me, but if you 
can try pinging me on IRC prior to freezing (just in case I'm awake and 
I've gotten a response about that patch and can push), that would be 
appreciated (do go ahead and freeze if I don't respond)


P.S. to Andrea - I will write a NEWS file entry, but I guess that can be 
safely pushed after Daniel freezes :-)




  That said they are supposed to mess with my internet tomorrow morning
and I'm travelling till the end of the week, but the above plan should
be doable. Hope that's okay with everybody.

  Then usually December is a low productivity month, and Feb is short,
so it is tempting to do like for previous years i.e. release mid-january
and end of Feb, except the Jan release will be 3.0.0.

Works for everybody ?

Daniel



--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release(s)

[Daniel Veillard]

 I'm late  so I think that if we don't want to slip too much
the best would be to enter freeze tomorrow (Tuesday) then have RC2
around Thursday and a release over the week-end.

 That said they are supposed to mess with my internet tomorrow morning
and I'm travelling till the end of the week, but the above plan should
be doable. Hope that's okay with everybody.

 Then usually December is a low productivity month, and Feb is short,
so it is tempting to do like for previous years i.e. release mid-january
and end of Feb, except the Jan release will be 3.0.0.

   Works for everybody ?

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  Time flies, I didn't realized we were that close from the end of the month.
So if we want to have 2.3.0 for next Monday I think we should start the freeze
today, possibly tonight.

   Does this work ? Sorry for late notice,

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Michal Privoznik]

On 29.03.2016 14:29, Daniel Veillard wrote:
>   I'm a bit behind, I forgot !
> I think we should freeze tomorrow (Wed 30), then make an rc2 on Friday
> and shoot for a release next Monday (Apr 4),
> 
>works for everybody ?

Yay, first release with NSS module.

Michal

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  I'm a bit behind, I forgot !
I think we should freeze tomorrow (Wed 30), then make an rc2 on Friday
and shoot for a release next Monday (Apr 4),

   works for everybody ?

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  I'm a bit late, sorry, but I think we should freeze on Thursday
for the next release, and then shoot for middle of next week for the
actual release,
  I hope this last moment warning isn't a problem,

  thanks,

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Andrea Bolognani]

On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote:
   We are getting close to the end of the month, so we may need to 
 freeze
 next Monday or Tuesday.

I guess a requirement for freeze, or at least for release, is
deciding how we want to handle symlinks with long paths[1] so
that we can, you know, make dist :)

Cheers.


[1] https://www.redhat.com/archives/libvir-list/2015-July/msg00869.html
-- 
Andrea Bolognani
Software Engineer - Virtualization Team

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Laine Stump]

On 07/24/2015 07:28 AM, Andrea Bolognani wrote:
 On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote:
   We are getting close to the end of the month, so we may need to 
 freeze
 next Monday or Tuesday.
 I guess a requirement for freeze, or at least for release, is
 deciding how we want to handle symlinks with long paths[1] so
 that we can, you know, make dist :)

It needs to be fixed far before the release - make rpm is broken too,
and that's my preferred method of testing.

I've fixed it locally with a patch to change deconfigured-cpus to
down-cpus, but didn't want to push it unilaterally, even though the
build is broken.

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Andrea Bolognani]

On Fri, 2015-07-24 at 09:35 -0400, Laine Stump wrote:
 On 07/24/2015 07:28 AM, Andrea Bolognani wrote:
  On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote:
 We are getting close to the end of the month, so we may need to
   
   freeze
   next Monday or Tuesday.
  I guess a requirement for freeze, or at least for release, is
  deciding how we want to handle symlinks with long paths[1] so
  that we can, you know, make dist :)
 
 It needs to be fixed far before the release - make rpm is broken too,
 and that's my preferred method of testing.
 
 I've fixed it locally with a patch to change deconfigured-cpus to
 down-cpus, but didn't want to push it unilaterally, even though the
 build is broken.

I just sent a patch renaming it to nonpresent, which is still
short enough not to run into the lenght limit.

It's certainly going to be stuck in the moderation queue, so if
you have the permissions to do so please let it through :)

Cheers.

-- 
Andrea Bolognani
Software Engineer - Virtualization Team

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Daniel Veillard]

On Fri, Jul 24, 2015 at 01:28:51PM +0200, Andrea Bolognani wrote:
 On Wed, 2015-07-22 at 23:50 +0800, Daniel Veillard wrote:
We are getting close to the end of the month, so we may need to 
  freeze
  next Monday or Tuesday.
 
 I guess a requirement for freeze, or at least for release, is
 deciding how we want to handle symlinks with long paths[1] so
 that we can, you know, make dist :)
 
 Cheers.
 
 
 [1] https://www.redhat.com/archives/libvir-list/2015-July/msg00869.html

  Saw that, and IMHO we need to fix the filename :-)

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Martin Kletzander]

On Wed, Jul 22, 2015 at 12:08:46PM -0400, Laine Stump wrote:

On 07/22/2015 11:50 AM, Daniel Veillard wrote:

  We are getting close to the end of the month, so we may need to freeze
next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that
configure.ac targets 1.2.18, so a priori no, but would rather have a
clear answer :-)




Unfortunately we don't.  We're trying to achieve clean and extensible
design that we're not going to regret (or at least as late as
possible).


I had posted patches with 1.3.0 in the docs changes, but haven't
pushed them yet (no reviews :-( )



I'll have a look at them today, but be prepared to change that to
1.2.18 :)

Martin


--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


signature.asc
Description: PGP signature
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  We are getting close to the end of the month, so we may need to freeze
next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that
configure.ac targets 1.2.18, so a priori no, but would rather have a
clear answer :-)

  Thanks,

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Laine Stump]

On 07/22/2015 11:50 AM, Daniel Veillard wrote:
   We are getting close to the end of the month, so we may need to freeze
 next Monday or Tuesday. Are we ready for 1.3.0 now :-) ? I see that
 configure.ac targets 1.2.18, so a priori no, but would rather have a
 clear answer :-)

I had posted patches with 1.3.0 in the docs changes, but haven't
pushed them yet (no reviews :-( )

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] Plan for next release

[Daniel Veillard]

 So if we want to push the next release for May 1st, it seems we should enter
freeze over the w.e. or early Monday morning. Unless there is disagreement
I plan to proceed that way, hopefully getting next release on time :-)

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

  Oops, Feb is really short and I got caught, I think if we want a
release by beginning of March, i.e. next week we need to enter freeze
ASAP. So I'm suggesting to start the freeze tomorrow, for a release
on Monday if everything goes well !

  Hope this suits everybody,

   thanks,

Daniel


-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] Plan for next release

[Daniel Veillard]

 If we want to push 1.2.9 around Oct 1st, I suggest to be prepared
to enter freeze on the 25th, so there is a small week to push patches
if you want features in the freeze,

Daniel

-- 
Daniel Veillard  | Open Source and Standards, Red Hat
veill...@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list