[Development] Can a device mkspec go directly into stable?

Donald Carr sirspudd at gmail.com
Wed Jan 16 00:13:43 CET 2013


This only makes sense; it can't destabilize affairs and to cock block
yourself on potential market share seems ludicrous at best.

w00t
Donald

On Tue, Jan 15, 2013 at 9:38 AM, Frederik Gladhorn
<frederik.gladhorn at digia.com> wrote:
> Tirsdag 15. januar 2013 15.01.35 skrev Rafael Roquetto:
>> Hello,
>>
>> I have submitted the following device mkspec for review:
>> https://codereview.qt-project.org/#change,44840
>>
>> I am wondering if this ok that it has been submitted directly to the stable
>> branch. This is an orthognal* mkspec, so I personally don't see any problems
>> but I would like to discuss this before taking action.
>>
>> I also wonder if the same rationale applies for any orthogonal change.
>>
>> Any comments?
>
> Since this is quite unlikely to break anyone else's build, I'd say it should
> not be a problem.
>
> Generally speaking though only bug fixes should go into stable, so you'll have
> to declare it a build fix ;)
>
> Cheers
> Frederik
>
>
>
>>
>> Thanks,
>> Rafael
>>
>> * "Orthogonality is one of the most important properties that can help make
>>  even complex designs compact. In a purely orthogonal design, operations do
>>  not have side effects; each action (whether it's an API call, a macro
>>  invocation, or a language operation) changes just one thing without
>>  affecting others. There is one and only one way to change each property of
>>  whatever system you are controlling." - The Art of Unix Programming, Eric
>>  Raymond.
> --
> Best regards,
> Frederik Gladhorn
> Senior Software Engineer - Digia, Qt
> Visit us on: http://qt.digia.com
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development



More information about the Development mailing list