The next release 6.0.0 should land around 15 January (and 6.1.0 back
at the end of Feb), this means we should enter freeze soon, I suggest
tomorrow Friday, with the goal of an RC2 on Monday for a release on
Wednesday assuming everything is fine.
thanks Dan for the reminder :-) hope this works
We are getting close to the end of the month, I suggest to enter
freeze tomorrow Tuesday, the end of the week will be quiet due to
US ThanksGiving, that should give plenty of time to test !
So RC2 on Thursday and if all goes well a release on Monday 2nd !
Hope this works for everybody,
With the end of month coming soon, time to plan for next release,
I suggest to enter freeze tomorrow wed 28, the have an RC2 on Friday and
if everything looks good next Monday we can push 5.7.0
Hope this works for everybody,
Daniel
--
Daniel Veillard | Red Hat Developers Tools
Ideally if we want to push the next release on Monday, we should enter freeze
tomorrow, then push Rc2 on Friday and then if everything goes well we can
push 5.5.0 final next Monday.
Hopefully that plan works for everyone,
Daniel
--
Daniel Veillard | Red Hat Developers Tools
On Sat, May 25, 2019 at 09:34:36AM +0200, Daniel Veillard wrote:
> We should enter freeze for 5.4.0 beginning of next week, maybe Monday
> evening or Tuesday morning, then plan for RC2 around Wed - Thur for a w.e.
> release.
>
> Hope this works for everybody,
>
>thanks,
>
> Daniel
I
We should enter freeze for 5.4.0 beginning of next week, maybe Monday
evening or Tuesday morning, then plan for RC2 around Wed - Thur for a w.e.
release.
Hope this works for everybody,
thanks,
Daniel
--
Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/
On 4/25/19 4:11 PM, Daniel Veillard wrote:
I think we need to enter freeze soon if we want to release mid next week
if we do so tomorrow, then we can push rc2 on Monday and have a release
around May first.
Any problem with that plan ?
I've raised a problem with one specific commit:
I think we need to enter freeze soon if we want to release mid next week
if we do so tomorrow, then we can push rc2 on Monday and have a release
around May first.
Any problem with that plan ?
thanks,
Daniel
--
Daniel Veillard | Red Hat Developers Tools
So it's getting time to think about 5.1.0, I'm thinking about entering
freeze on Monday next week, push rc2 Wed and if everything goes well
we can have the release out on Friday 1st,
I hope that works for everyone,
Daniel
P.S. I will be on west coast so freeze and pushes likely to be
On 1/10/19 5:08 AM, Daniel P. Berrangé wrote:
On Wed, Jan 09, 2019 at 10:03:33PM -0500, Laine Stump wrote:
On 1/9/19 3:53 PM, Daniel Veillard wrote:
Happy New Year everybody,
as planned we should release 5.0.0 around Jan 15. This means that
the best to meet that deadline would be to
On Wed, Jan 09, 2019 at 10:03:33PM -0500, Laine Stump wrote:
> On 1/9/19 3:53 PM, Daniel Veillard wrote:
> > Happy New Year everybody,
> >
> >as planned we should release 5.0.0 around Jan 15. This means that
> > the best to meet that deadline would be to enter freeze tomorrow Thur,
> >
On 1/9/19 3:53 PM, Daniel Veillard wrote:
Happy New Year everybody,
as planned we should release 5.0.0 around Jan 15. This means that
the best to meet that deadline would be to enter freeze tomorrow Thur,
then have an RC2 over the w.e. and then if all goes well we can roll
out the
Happy New Year everybody,
as planned we should release 5.0.0 around Jan 15. This means that
the best to meet that deadline would be to enter freeze tomorrow Thur,
then have an RC2 over the w.e. and then if all goes well we can roll
out the release next Tuesday.
If there is no issue with
On 09/26/2018 01:58 PM, Andrea Bolognani wrote:
> On Wed, 2018-09-26 at 11:54 +0200, Michal Privoznik wrote:
>> On 09/26/2018 01:05 AM, John Ferlan wrote:
>>> So in summary, I believe the issues raised thus far are primarily
>>> metadata locking related, so should we really hold up the release for
On Wed, 2018-09-26 at 11:54 +0200, Michal Privoznik wrote:
> On 09/26/2018 01:05 AM, John Ferlan wrote:
> > So in summary, I believe the issues raised thus far are primarily
> > metadata locking related, so should we really hold up the release for
> > something that isn't fully complete or listed
John Ferlan [2018-09-25, 07:05PM -0400]:
> So, I assume we can still call this "feature" as a work in progress.
> Perhaps we need a new section in news.xml or some other means to
> indicate we have "experimental code" with "limited support" (similar to
> the QEMU development preview and/or the x-
On 09/26/2018 01:05 AM, John Ferlan wrote:
>
>
> On 9/25/18 9:38 AM, Daniel Veillard wrote:
>> On Tue, Sep 25, 2018 at 09:42:20AM +0200, Michal Privoznik wrote:
>>> On 09/24/2018 03:42 PM, Daniel Veillard wrote:
that's next week ! If we want to release around Oct 1st, I would
suggest
On 9/25/18 9:38 AM, Daniel Veillard wrote:
> On Tue, Sep 25, 2018 at 09:42:20AM +0200, Michal Privoznik wrote:
>> On 09/24/2018 03:42 PM, Daniel Veillard wrote:
>>> that's next week ! If we want to release around Oct 1st, I would
>>> suggest to enter freeze this Wed, probably in the morning
On Tue, Sep 25, 2018 at 09:42:20AM +0200, Michal Privoznik wrote:
> On 09/24/2018 03:42 PM, Daniel Veillard wrote:
> > that's next week ! If we want to release around Oct 1st, I would
> > suggest to enter freeze this Wed, probably in the morning europe time,
> > then plan for an RC2 friday
On 09/24/2018 03:42 PM, Daniel Veillard wrote:
> that's next week ! If we want to release around Oct 1st, I would
> suggest to enter freeze this Wed, probably in the morning europe time,
> then plan for an RC2 friday morning and if everything goes well, have
> the final release next monday.
>
>
that's next week ! If we want to release around Oct 1st, I would
suggest to enter freeze this Wed, probably in the morning europe time,
then plan for an RC2 friday morning and if everything goes well, have
the final release next monday.
I hope that works for everybody !
Daniel
--
Daniel
So we are getting very close to the end of the month,
I suggest to enter freeze tomorrow morning, then plan for an RC2
on Tuesday, that way if everythiong goes well next release
would be on Thursday 2nd Aug,
I hope this is fine with everyone's schedule,
thanks,
Daniel
--
Daniel
Though May 1st is usually closed for most countries, let's try to shoot
for a next release around that time. Best might be to enter freeze tomorrow
morning (my time), allowing for 2 days of reviews, then an RC2 over the
week-end and if there is nothing serious shoot for a release around Tues.
I was reminded that the end of the month is very soon :-)
I suggest to enter freeze tomorrow morning, then going RC2 on Thursday
and then push the release over the week-end or Monday morning
hope this works for all !
Daniel
--
Daniel Veillard | Red Hat Developers Tools
Hi all,
we are getting close to the end of the month, and I think we should
enter freeze over the week-end. Then I can try to push an RC2 on Tuesday
and make the GA release on the 2nd Nov (I'm travelling ATM and Nov 1st
is closed, not sure I could do this that day).
Hope this works for
On 09/28/2017 01:01 PM, Daniel Veillard wrote:
> On Thu, Sep 28, 2017 at 03:15:10PM +0200, Peter Krempa wrote:
>> On Thu, Sep 28, 2017 at 12:17:41 +0200, Daniel Veillard wrote:
>>> I'm a bit late, again ...
>>>
>>> I think we should enter freeze late today, then I can make an rc2 this week
>>>
On Thu, Sep 28, 2017 at 03:15:10PM +0200, Peter Krempa wrote:
> On Thu, Sep 28, 2017 at 12:17:41 +0200, Daniel Veillard wrote:
> > I'm a bit late, again ...
> >
> > I think we should enter freeze late today, then I can make an rc2 this week
> > end and shoot for a release on the 3rd
> >
> > I
On Thu, Sep 28, 2017 at 12:17:41 +0200, Daniel Veillard wrote:
> I'm a bit late, again ...
>
> I think we should enter freeze late today, then I can make an rc2 this week
> end and shoot for a release on the 3rd
>
> I hope there is no issue with this,
Please wait until John pushes the
I'm a bit late, again ...
I think we should enter freeze late today, then I can make an rc2 this week
end and shoot for a release on the 3rd
I hope there is no issue with this,
thanks,
Daniel
--
Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/
On Wed, Jul 26, 2017 at 10:15:37PM +0200, Peter Krempa wrote:
> On Tue, Jul 25, 2017 at 23:47:12 +0800, Daniel Veillard wrote:
> > The end of the month is next week, so if we want to release around
> > Aug 1st, I think we should enter freeze on Thursday morning, then
> > I could make rc2 on
On Tue, Jul 25, 2017 at 23:47:12 +0800, Daniel Veillard wrote:
> The end of the month is next week, so if we want to release around
> Aug 1st, I think we should enter freeze on Thursday morning, then
> I could make rc2 on Saturday and we could have the release on the Tuesday
> or Wed.
>
The end of the month is next week, so if we want to release around
Aug 1st, I think we should enter freeze on Thursday morning, then
I could make rc2 on Saturday and we could have the release on the Tuesday
or Wed.
Usually this is not the busiest time of the year but if this is a problem
I'm already a bit late, I think we should try to enter freeze at the end
of the day, then push rc2 on friday end or w.e. which would then allow to have
the final release on Monday or Tuesday. I assume US won't work those days
but that should be fine if we don't have any blocker,
hopefully
we are getting close to the end of the month, so in order to ship
on time I suggest we enter freeze on Friday (late or w.e.) then plan
an RC2 around Tuesday, for a final release on Thursday if everything
goes well,
hope this works for everybody, there is a few days to push patches
in time for
I didn't realized that end of month was getting that close. So I suggest
to enter freeze for 3.3.0 on Friday. I can then push an RC2 on Monday evening
or Tuesday and push the release Wed or Thursday,
I hope that works for everybody, there is roughtly 2 days to push patches
you want in (except
Since we had planned a release mid January, it's time to plan
the next release, I suggest to shoot for a release next Monday, the
16th. In which case we should enter freeze this Wednesday, then
have RC2 on Friday, and then if everything is fine, push the release
next Monday.
Hope this works
I will be in vacation this week, but should be able to make the release
candidate
on Thursday, which means that if I can make a CR2 release on the week-end, we
should
be able to push 2.4.0 around Nov 1st if everything looks good.
There is a few tests who went red in
On 08/24/2016 11:08 AM, Michal Privoznik wrote:
On 24.08.2016 11:28, Daniel Veillard wrote:
So if we want a 2.2.0 release around Sep 1st, I suggest entering freeze this
Friday
probably at the end of the day (european time), then push the rc2 next Tuesday
for a
release on Thursday,
hope
On Wed, Aug 24, 2016 at 05:08:17PM +0200, Michal Privoznik wrote:
> On 24.08.2016 11:28, Daniel Veillard wrote:
> > So if we want a 2.2.0 release around Sep 1st, I suggest entering freeze
> > this Friday
> > probably at the end of the day (european time), then push the rc2 next
> > Tuesday for
On 24.08.2016 11:28, Daniel Veillard wrote:
> So if we want a 2.2.0 release around Sep 1st, I suggest entering freeze
> this Friday
> probably at the end of the day (european time), then push the rc2 next
> Tuesday for a
> release on Thursday,
>
> hope this works for everybody,
Nearly
So if we want a 2.2.0 release around Sep 1st, I suggest entering freeze this
Friday
probably at the end of the day (european time), then push the rc2 next Tuesday
for a
release on Thursday,
hope this works for everybody,
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
On 06/22/2016 04:02 AM, Daniel Veillard wrote:
> So based on the new numbering scheme we should push 2.0.0 at the
> end of the month. Due to travel and move, I am tempted to enter the
> freeze on next Sunday (or Monday) to try to push for the release on
> Friday 1st or the week-end.
>
>
On 06/22/2016 02:02 AM, Daniel Veillard wrote:
> So based on the new numbering scheme we should push 2.0.0 at the
> end of the month. Due to travel and move, I am tempted to enter the
> freeze on next Sunday (or Monday) to try to push for the release on
> Friday 1st or the week-end.
This would
So based on the new numbering scheme we should push 2.0.0 at the
end of the month. Due to travel and move, I am tempted to enter the
freeze on next Sunday (or Monday) to try to push for the release on
Friday 1st or the week-end.
Hope this works for everyone,
Daniel
--
Daniel Veillard
While 1.3.3 went out a bit late I think we should try to stick to
the month boundary for releases. I will be travelling next week so
to avoid any deviation the best would be to release on Sunday may 1st
So that mean we need to freeze real soon now for 1.3.4 and I suggest
to do that tomorrow
So we are getting close to the end of the month and it's time to push
a new release. I think that if we want to push it by March 1st we should
start the freeze Wednesday at the latest, maybe RC1 on Wed, RC2 friday
and release next Mon if everything looks okay.
If there is an issue with this
On Sun, 2016-01-10 at 09:56 +0800, Daniel Veillard wrote:
> So we should push 1.3.1 by the middle of this month (with 1.3.2 for
> end of Feb as decided when we planned 1.3.0) which means we should enter
> freeze soon. I am suggesting to start the freeze in Tuesday, with rc2 on
> Thursday and
So we should push 1.3.1 by the middle of this month (with 1.3.2 for
end of Feb as decided when we planned 1.3.0) which means we should enter
freeze soon. I am suggesting to start the freeze in Tuesday, with rc2 on
Thursday and having the release by next week-end,
if anybody has an issue with
Seems we should push 1.2.19 at the end of the month, we are right
now at around 150 commits so not a big release. Thus I suggest to enter
freeze Wed next week for a release around Sep 1st.
I hope this works for everybody,
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
On Thu, Jun 25, 2015 at 09:50:42PM +0200, Martin Kletzander wrote:
[adding Dan to Cc as he asked me about this right before I had to
leave for an appointment]
On Thu, Jun 25, 2015 at 10:08:10PM +0800, Daniel Veillard wrote:
Sorry I nearly forgot, but we should enter freeze soon to try to
On Fri, Jun 26, 2015 at 09:51:26AM +0100, Daniel P. Berrange wrote:
On Thu, Jun 25, 2015 at 09:50:42PM +0200, Martin Kletzander wrote:
[adding Dan to Cc as he asked me about this right before I had to
leave for an appointment]
On Thu, Jun 25, 2015 at 10:08:10PM +0800, Daniel Veillard wrote:
On Fri, Jun 26, 2015 at 11:06:01AM +0200, Martin Kletzander wrote:
On Fri, Jun 26, 2015 at 09:51:26AM +0100, Daniel P. Berrange wrote:
On Thu, Jun 25, 2015 at 09:50:42PM +0200, Martin Kletzander wrote:
[adding Dan to Cc as he asked me about this right before I had to
leave for an appointment]
[adding Dan to Cc as he asked me about this right before I had to
leave for an appointment]
On Thu, Jun 25, 2015 at 10:08:10PM +0800, Daniel Veillard wrote:
Sorry I nearly forgot, but we should enter freeze soon to try to
hit the end of the month target. I see that Martin's APIs for admin
Sorry I nearly forgot, but we should enter freeze soon to try to
hit the end of the month target. I see that Martin's APIs for admin support
has been merged in so that would be libvirt-1.3.0.
Plan is to enter freeze this w.e. and try to release by the end of the week,
I hope this works for
On 28.05.2015 23:08, Jim Fehlig wrote:
On 05/28/2015 05:33 AM, Michal Privoznik wrote:
On 27.05.2015 20:45, Jim Fehlig wrote:
On 05/23/2015 07:22 AM, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on
Tuesday
for an 1.2.16 on June
On 05/28/2015 05:33 AM, Michal Privoznik wrote:
On 27.05.2015 20:45, Jim Fehlig wrote:
On 05/23/2015 07:22 AM, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15
On 27.05.2015 20:45, Jim Fehlig wrote:
On 05/23/2015 07:22 AM, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15 but
sticking to the monthly release is
On Thu, May 28, 2015 at 01:33:52PM +0200, Michal Privoznik wrote:
On 27.05.2015 20:45, Jim Fehlig wrote:
On 05/23/2015 07:22 AM, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have
On 05/23/2015 07:22 AM, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15 but
sticking to the monthly release is important.
Hi Daniel,
I have a few old patches
On Sat, May 23, 2015 at 09:22:00PM +0800, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15 but
sticking to the monthly release is important.
I hope this works for
On Sat, May 23, 2015 at 03:42:47PM -0400, Martin Kletzander wrote:
On Sat, May 23, 2015 at 09:22:00PM +0800, Daniel Veillard wrote:
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15 but
Hi everybody,
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15 but
sticking to the monthly release is important.
I hope this works for everybody,
thanks,
Daniel
--
Daniel Veillard | Open
if we want to get it by next month, we should probably freeze on Tuesday
for an 1.2.16 on June 1st, we 'only' have 137 commits since 1.2.15 but
sticking to the monthly release is important.
I hope this works for everybody,
thanks,
Daniel
--
Daniel Veillard | Open Source and
So we already have around 300 commits made since 1.2.13, and
the end of the month is coming, so I guess we should enter freeze
soon.
I would suggest to do this friday to try to shoot for a 1.2.14
release by April 1st - always a great date to ship a release !
any opposition to this plan ?
It's start to think pushing a new release. Last one was mid-december
so we ought to push one this month, I will be travelling the last week
and since February is short I suppose pushing the release a bit early
is not a problem. We have around 180 commits already, and I would like
to push for
I suggest to enter freeze Monday next week, on the 26 allowing
for a release of 1.2.5 early in the morning of June 2nd
Does that work for everybody ?
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veill...@redhat.com | libxml Gnome XML XSLT toolkit
66 matches
Mail list logo
