I'm a little behind, I was on vacations last week and kind of forgot ...
So I think the best will be to enter freeze tomorrow morning (29 Aug),
then have an RC2 on the 31, and make the release over the week-end.
I assume this works for everybody, otherwise raise your voice :-)
thanks,
Da
Hi everybody,
it's about time to think about 3.1.0, I think to be on the safe side for a
March 1st release we should enter freeze at the end of the week, most likely
on Friday, so if you have patches that need to get in, please make sure
they are approved and pushed in time.
Hope this works
On Mon, Jul 25, 2016 at 11:48:38PM +0100, Justin Clift wrote:
> On 25 Jul 2016, at 23:13, Daniel Veillard wrote:
> > About time to roll that one.
> > I think we need to enter freese on Wednesday, then I can make rc2 on Friday,
> > and hopefully we can push 2.1.0 on Monday or Tuesday next week.
>
Justin Clift wrote:
> On 25 Jul 2016, at 23:13, Daniel Veillard wrote:
> > About time to roll that one.
> > I think we need to enter freese on Wednesday, then I can make rc2 on Friday,
> > and hopefully we can push 2.1.0 on Monday or Tuesday next week.
> >
> > Raise a flag if that doesn't wo
On 25 Jul 2016, at 23:13, Daniel Veillard wrote:
> About time to roll that one.
> I think we need to enter freese on Wednesday, then I can make rc2 on Friday,
> and hopefully we can push 2.1.0 on Monday or Tuesday next week.
>
> Raise a flag if that doesn't work :-)
Hoping we get the OSX fix i
About time to roll that one.
I think we need to enter freese on Wednesday, then I can make rc2 on Friday,
and hopefully we can push 2.1.0 on Monday or Tuesday next week.
Raise a flag if that doesn't work :-)
thanks,
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
vei
Sorry about the late notice, I forgot about the end of month
coming. It seems we are trying a lot of patches in right now,
but it would be good to not drift too much, so I am suggesting
to enter the freeze on Monday morning. This mean I could push
1.2.4 either on Friday if everything looks really
On Mon, Oct 28, 2013 at 12:30:33PM +, Daniel P. Berrange wrote:
> On Fri, Oct 18, 2013 at 05:18:22PM -0400, Daniel Veillard wrote:
> > Assuming we want to release around the end of the month means we
> > ought to enter freeze next week around the 24 or 25, but I know I
> > will be very busy an
On Mon, Oct 28, 2013 at 7:30 AM, Daniel P. Berrange wrote:
> On Fri, Oct 18, 2013 at 05:18:22PM -0400, Daniel Veillard wrote:
>> Assuming we want to release around the end of the month means we
>> ought to enter freeze next week around the 24 or 25, but I know I
>> will be very busy and have a ha
On Fri, Oct 18, 2013 at 05:18:22PM -0400, Daniel Veillard wrote:
> Assuming we want to release around the end of the month means we
> ought to enter freeze next week around the 24 or 25, but I know I
> will be very busy and have a hard time on those days. So potentially
> I will try to do the free
Assuming we want to release around the end of the month means we
ought to enter freeze next week around the 24 or 25, but I know I
will be very busy and have a hard time on those days. So potentially
I will try to do the freeze on the Saturday 26 for a release around
Nov 1st, but there is a slight
If we want to stick to the end of the month schedule we need to
enter freeze for 1.1.3 next week, I suggest to do this early on Wed 25
so that we can plan on pushing 1.1.3 on the Tue 1st Oct
So unless there is a serious issue, let's plan to freeze next Wed,
Daniel
--
Daniel Veillard | O
To try to stay on the end of month release schedule, I am suggesting
to enter the freeze for 1.1.2 next Tuesday, i.e. the 27th Aug, and
then shoot for a release on the morning of Monday 2nd of Sep.
So unless I hear disagreements, that's the plan :-)
Daniel
--
Daniel Veillard | Open Sour
Time to plan the release at the end of the month, for a change I
would prefer to release a bit earlier and shoot for Tue 30th July.
So this would mean that we enter the freeze on Wednesday 24 next week,
hopefully that is fine for everybody, if people have pending patche(s)
that still need revie
On 20/06/13 02:17, Daniel Veillard wrote:
If we want to release at the end of the month as usual, we should
probably enter freeze next Monday or Tuesday. There is however some
patch set needing review, e.g. the 'Guest Panicked' one or the big
fine grained ACL feature. Dan do you think this can
If we want to release at the end of the month as usual, we should
probably enter freeze next Monday or Tuesday. There is however some
patch set needing review, e.g. the 'Guest Panicked' one or the big
fine grained ACL feature. Dan do you think this can reasonably be merged
in by next Monday ?
On 23/05/13 03:59, Daniel Veillard wrote:
It seems that if we want to have the release at the end of the month
we ought to enter freeze next Monday the 27 for a release on the 3rd
(I may have a hard time making the release on Friday 31 or w.e.).
Is there any problem with freezing next Monday ?
On 22.05.2013 21:59, Daniel Veillard wrote:
> It seems that if we want to have the release at the end of the month
> we ought to enter freeze next Monday the 27 for a release on the 3rd
> (I may have a hard time making the release on Friday 31 or w.e.).
> Is there any problem with freezing next M
It seems that if we want to have the release at the end of the month
we ought to enter freeze next Monday the 27 for a release on the 3rd
(I may have a hard time making the release on Friday 31 or w.e.).
Is there any problem with freezing next Monday ? If not let's proceed
that way, in that case
On 2012年08月15日 17:05, Daniel Veillard wrote:
I would rather have the release a bit earlier than expected,
I was initially hoping to get a new set of localization for
Sep 4 but it is clear at this point that we won't have them
in time. Since we have been working on 0.10.0 for 6 weeks now,
I thin
I would rather have the release a bit earlier than expected,
I was initially hoping to get a new set of localization for
Sep 4 but it is clear at this point that we won't have them
in time. Since we have been working on 0.10.0 for 6 weeks now,
I think pushing it 2 weeks from now is reasonnable, so
On 04/27/2012 11:34 PM, Daniel Veillard wrote:
I'm not really able to make a good review of remaining patches sent
on the list and not pushed today, but I would like to check the pvs
driver set patches before entering the freeze, so I'm postponing it
until after the week-end, possibly on Mond
On Fri, Apr 20, 2012 at 05:22:29PM +0800, Daniel Veillard wrote:
> Assuming we try to stay on a monthly schedule, then I would
> suggest to enter the freeze around next Friday (27th April)
> and shoot for a release around the 4th of May.
> I'm supposed to be in vacation most of next week, but I
Assuming we try to stay on a monthly schedule, then I would
suggest to enter the freeze around next Friday (27th April)
and shoot for a release around the 4th of May.
I'm supposed to be in vacation most of next week, but I think
I will still be able to make the release candidate 1
We have a n
Hello,
following a bit too much backlog on libxml2 for the last years and
an happy familly event, I have been a bit sidetracked in the last weeks
and will be in the near future.
I know there is a tons of pending patches, updates for drives and
cleanups waiting for a release. I will try to make
25 matches
Mail list logo
