[Development] Towards a Qt 5 beta

[Stephen Kelly]

On Thursday, April 12, 2012 18:49:34 lars.knoll at nokia.com wrote:
> On 4/12/12 5:06 PM, "ext Oswald Buddenhagen"
> 
> <oswald.buddenhagen at nokia.com> wrote:
> >On Thu, Apr 12, 2012 at 04:26:12PM +0200, ext Stephen Kelly wrote:
> >> I'd like to see another model attempted next time, like all commits
> >> going to master, and a 'stable' branch which gets fast forwarded once
> >> a week
> >
> >that's besides the point. people must work on the bleeding edge.
> >bic/sic changes just don't fare well with downstream (whichever
> >definition of that you apply), so they are diverted into a separate
> >branch.
> 
> Yes, having a stable that's simply one week behind has no value.

I said one week because IIRC that was the initially intended rate for the 
api_changes merge.

But to be more clear: ... a 'stable' branch which gets fast forwarded at 
appropriate times.

> Then
> people could just as well not sync to the latest code base. 

Yes.

> Downstream
> projects (declarative is downstream from qtbase) need to be able to follow
> bleeding edge (e.g. in the CI). 

I'm not sure what you mean when you say bleeding edge. Do you mean 'master'?

> But you don't want to have to recompile
> the whole stack every two hours.

Maybe you just picked a number, but two hours is roughly how long it takes for 
CI to run, so not really realistic, except for CI systems which rebuild from 
scratch anyway :). 

I don't see why a developer would need to be on the bleeding edge at all times 
unless they wanted the latest API changes, in which case they would rather 
need to follow the api_changes branch in the current model.

This is just food for thought anyway, for when the need for branch set-up 
arises again.

Thanks,

-- 
Stephen Kelly <stephen.kelly at kdab.com> | Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-Independent Software Solutions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120416/527bb2a6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120416/527bb2a6/attachment.sig>