[Development] Setting up time-based releases for the project

lars.knoll at nokia.com lars.knoll at nokia.com
Wed Aug 8 09:33:40 CEST 2012


On Aug 7, 2012, at 5:12 PM, ext Rick Stockton <rickstockton at reno-computerhelp.com> wrote:
> On 08/06/2012 02:22 PM, joao.abecasis at nokia.com wrote:
>> Hello Qt-ians,
>> << SNIP >>
>> 
>> * The branches
>> 
>> The three branches define a progression of decreasing rate-of-change and
>> thus increasing stability.
>> 
>> - Fire hose - the main development branch. It supports the minor release
>>   cycle. The commit policy allows for features and bug fixes. Changes
>>   must support BC promises for minor releases.
>> 
>>   This is the default branch for all changes.
> Just to highlight this: Changes in 5.1 must be Binary Compatible for 
> software compiled and built under 5.0, yes?

Yes.

> (Some months ago, it was still uncertain whether 5.1 would actually be 
> like a "major release", with 5.0 more of a "preview".)

I don't see any real argument for doing something like this.

Cheers,
Lars




More information about the Development mailing list