[Development] [Releasing] HEADS UP: Qt 5.4 feature freeze - branch created

[Oswald Buddenhagen]

On Sun, Aug 10, 2014 at 03:41:02PM +0000, Knoll Lars wrote:
> On 10/08/14 17:02, "Thiago Macieira" <thiago.macieira at intel.com> wrote:
> >On Sunday 10 August 2014 14:27:51 Knoll Lars wrote:
> >> >It should, since it reflects the agreed-upon way of doing things.
> >> >It's also how we've done it for the past 4 feature releases. You
> >> >can't change the procedure without announcing ahead of time and
> >> >letting people comment.
> >> 
> >> I think I’m missing a mail here. But if this is about me asking for
> >> a different class name for QvolumeInfo, I don’t see this as an
> >> issue (see below).
> >
> >It's about integrating the class. When Marc asked for a freeze
> >exception, I suggested and you agreed that we would have the weekend
> >to work on this and that the 5.4 branch would be created on Monday.
> >Just like it was done for the past 4 feature releases.
> >
> >Well, the branch was created on Saturday halfway through the day and
> >the "dev" branch moved to 5.5 through administrative action. That's
> >the first time this happens and there was no discussion or prior
> >warning.
> 
> Yeah, that caught me a bit by surprise as well.
>
why would it? the plan was set and announced (regardless how poorly it
was executed on previous occasions). that plan didn't include any
specific delay between locking down and actually branching.
what's more, now that we don't rely on downmerging any more, the dev
lockdown is technically a purely "flagging" operation (with the sole
objective of avoiding cherry-picks), and certainly not an opportunity to
smuggle in some late-comers (even though i actually did that with many
changes, because i didn't feel like doing something else on my weekend).

> >We lose 24 hours worth of integration+fix attempts and another 36
> >hours due to my unavailability in the new integration window. So
> >other people please take care of reviewing and approving Ivan's
> >changes in the next 48 hours.
> 
> As said, I’m ok to commit it to the 5.4 branch during the next week.
> 
to me this is a rather obvious interpretation of "freeze exception",
which is why it's beyond me why anyone would get upset about me NOT
holding up integrations on dev even longer than planned (which would be
a logical consequence of delaying the 5.4 branch creation).

speaking of which, dev will be opened again early tuesday.

fwiw, the first batch of retargetings is done. you can already stage,
even though it probably won't start integrating until monday.