> On 30 May 2017, at 09:15, Tony Sarajärvi wrote:
>
> Hi all!
>
> I was due to write you something about the CI. This time I’ll cover the
> topics performance as well as upcoming hardware and software changes.
>
> Performance:
>
> You have all noticed that the CI
On Wednesday, 31 May 2017 05:50:35 PDT Oswald Buddenhagen wrote:
> On Wed, May 31, 2017 at 02:38:53PM +0200, Robin Burchell wrote:
> > To me, it's implicit that each release will ideally have improvements in
> > terms of stability, so I think that there's less point in focusing on
> > them, unless
> -Original Message-
> From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt-
> project.org] On Behalf Of Robin Burchell
> Sent: Wednesday, 31 May 2017 3:02 PM
> To: development@qt-project.org
> Subject: Re: [Development] Please add [ChangeLog] entries to your commits!
>
>
On Wed, May 31, 2017, at 02:50 PM, Oswald Buddenhagen wrote:
> On Wed, May 31, 2017 at 02:38:53PM +0200, Robin Burchell wrote:
> > To me, it's implicit that each release will ideally have improvements in
> > terms of stability, so I think that there's less point in focusing on
> > them, unless
On Wed, May 31, 2017 at 02:38:53PM +0200, Robin Burchell wrote:
> To me, it's implicit that each release will ideally have improvements in
> terms of stability, so I think that there's less point in focusing on
> them, unless they are a major newsworthy item: something like "sorry we
> released
My rule of thumb (when editing qtdeclarative's, for the last releases)
has been to include things depending on the "size" of the release. Small
(patch level) release? Include more bugs. Large (.0) release? Less focus
on bugs, more focus on architectural changes, feature additions, etc.
Any
Hi all,
I am happy to announce Qt 5.9.0 is released today, see
http://blog.qt.io/blog/2017/05/31/qt-5-9-released/
Big thanks everyone involved!
Br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org