Re: [Development] Qt QML Maintainer change

[Frederik Gladhorn]

This is great news, I'm happy to see Ulf taking over while Simon will be able 
to give advice.

+1 (in case that wasn't clear)

Cheers,
Frederik

On mandag 18. februar 2019 14:25:15 CET Simon Hausmann wrote:
> Hi,
> 
> I'd like to step down as the maintainer of the Qt QML module and pass the
> torch on to Ulf Hermann.
> 
> He has been contributing to the module since 2013 with countless features,
> bug fixes, reviews and re-designs. He's absolutely awesome to work with and
> his lines break sharply at 100 characters ;-)
> 
> 
> Simon




___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Mitch Curtis]

> -Original Message-
> From: Development  On Behalf Of
> Shawn Rutledge
> Sent: Thursday, 21 February 2019 1:45 PM
> To: development@qt-project.org
> Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
> 
> 
> > On 21 Feb 2019, at 12:47, Cristián Maureira-Fredes  fre...@qt.io> wrote:
> >
> > Hello,
> >
> > so, we agree the Go one (qtqa) is the recommended one?
> >
> > Time ago, I was directed to this one:
> > http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/create_cha
> > ngelog.pl and ended up suggesting this one as a replacement for the Qt
> > for Python project: https://codereview.qt-project.org/#/c/252162/
> >
> > I understand it is better to focus on one script and improve it so
> > that's why I would like to know which is the preferred option.
> 
> I wanted to automate the manual work I’d been doing for every release to
> get most of the bug fixes listed in the changelog (including those which don’t
> have changelog entries in the commit message); and I’d rather write Go than
> Perl, so I did a couple of patches on that tool.  (The last change is just now
> integrated.)  It works for me, but it intentionally strays on the side of “too
> much information.”  It combines the git commit message with the Jira bug
> description, so those entries always needs editing to get a concise changelog
> message.  For me that’s fine, because neither Jira bug descriptions nor
> commit messages are written in the right style for a changelog, but at least 
> all
> the information gets into the file so that I don’t have to individually look 
> up
> bugs on Jira to find out what certain changes were really about (as long as 
> the
> subject is descriptive enough).
> 
> So I don’t know if every maintainer would like to work that way; maybe some
> would rather stray on the side of having the generation mostly automated
> and not adding every bug fix?  But in practice it seems e.g. the qtbase
> changelog has always needed plenty of manual editing.  So having the
> changelog a bit rough at first won’t be any more work than what’s been
> going on.
> 
> https://codereview.qt-project.org/#/c/253930/ PS2 is currently showing
> exactly the output of this tool, so you can compare PS1 to PS2 to see the
> difference.
> 
> The boilerplate does need a little work.  So far I didn’t think we would
> actually use this tool for the whole log, I just wanted to use it to get some
> more entries to blend into the existing log.  But if we want to use it for 
> real,
> fixing it up a little more won’t be hard.

I think this is a good addition. I also found myself looking up bug reports to 
see how else I could phrase the message. At a minimum the tense has to be fixed 
for each entry ("Fix" or other verb => "Fixed") anyway.

> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Shawn Rutledge]

> On 21 Feb 2019, at 12:47, Cristián Maureira-Fredes 
>  wrote:
> 
> Hello,
> 
> so, we agree the Go one (qtqa) is the recommended one?
> 
> Time ago, I was directed to this one: 
> http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/create_changelog.pl
> and ended up suggesting this one as a replacement for the Qt for Python 
> project: https://codereview.qt-project.org/#/c/252162/
> 
> I understand it is better to focus on one script and improve it so that's why 
> I would like to know
> which is the preferred option.

I wanted to automate the manual work I’d been doing for every release to get 
most of the bug fixes listed in the changelog (including those which don’t have 
changelog entries in the commit message); and I’d rather write Go than Perl, so 
I did a couple of patches on that tool.  (The last change is just now 
integrated.)  It works for me, but it intentionally strays on the side of “too 
much information.”  It combines the git commit message with the Jira bug 
description, so those entries always needs editing to get a concise changelog 
message.  For me that’s fine, because neither Jira bug descriptions nor commit 
messages are written in the right style for a changelog, but at least all the 
information gets into the file so that I don’t have to individually look up 
bugs on Jira to find out what certain changes were really about (as long as the 
subject is descriptive enough).

So I don’t know if every maintainer would like to work that way; maybe some 
would rather stray on the side of having the generation mostly automated and 
not adding every bug fix?  But in practice it seems e.g. the qtbase changelog 
has always needed plenty of manual editing.  So having the changelog a bit 
rough at first won’t be any more work than what’s been going on.

https://codereview.qt-project.org/#/c/253930/ PS2 is currently showing exactly 
the output of this tool, so you can compare PS1 to PS2 to see the difference.

The boilerplate does need a little work.  So far I didn’t think we would 
actually use this tool for the whole log, I just wanted to use it to get some 
more entries to blend into the existing log.  But if we want to use it for 
real, fixing it up a little more won’t be hard.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Mitch Curtis]

> -Original Message-
> From: Cristián Maureira-Fredes
> Sent: Thursday, 21 February 2019 12:47 PM
> To: Mitch Curtis ; Jani Heikkinen ;
> development@qt-project.org
> Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
> 
> Hello,
> 
> so, we agree the Go one (qtqa) is the recommended one?

I think we need to wait to see what Jani says, but I added a section to the Qt 
5 Releasing page in anticipation. :D

https://wiki.qt.io/Qt5Releasing#Change_log_generation

> Time ago, I was directed to this one:
> http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-
> tools/create_changelog.pl
> and ended up suggesting this one as a replacement for the Qt for Python
> project: https://codereview.qt-project.org/#/c/252162/
> 
> I understand it is better to focus on one script and improve it so that's why 
> I
> would like to know which is the preferred option.
> 
> Cheers
> 
> 
> From: Development  on behalf of
> Mitch Curtis 
> Sent: 21 February 2019 11:46
> To: Jani Heikkinen; development@qt-project.org
> Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
> 
> > -Original Message-
> > From: Jani Heikkinen
> > Sent: Thursday, 21 February 2019 11:06 AM
> > To: Mitch Curtis ; development@qt-project.org
> > Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> > > -Original Message-
> > > From: Mitch Curtis 
> > > Sent: torstai 21. helmikuuta 2019 11.21
> > > To: Mitch Curtis ; Jani Heikkinen
> > > ; development@qt-project.org
> > > Subject: RE: [Development] Maintainers, your action needed: Qt
> > > 5.12.2 changes files
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: Development  On
> Behalf
> > > Of
> > > > Mitch Curtis
> > > > Sent: Thursday, 21 February 2019 9:33 AM
> > > > To: Jani Heikkinen ;
> > > > development@qt-project.org
> > > > Subject: Re: [Development] Maintainers, your action needed: Qt
> > > > 5.12.2 changes files
> > > >
> > > > > -Original Message-
> > > > > From: Development  On
> > Behalf
> > > > Of
> > > > > Jani Heikkinen
> > > > > Sent: Thursday, 21 February 2019 9:19 AM
> > > > > To: development@qt-project.org
> > > > > Subject: [Development] Maintainers, your action needed: Qt
> > > > > 5.12.2 changes files
> > > > >
> > > > > Hi,
> > > > > Initial ones here: https://codereview.qt-
> > > > >
> project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> > > > >
> > > > > Please take it over, do needed modifications and get '+2' during
> > > > > this
> > > week.
> > > >
> > > > Do we have a script that generates the change logs? I see that
> > > > qtbase has entries for bug fixes with the task number:
> > > >
> > > > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.
> > > > 12
> > > > .1
> > > >
> > > > I'd like to get the same for the modules that I maintain. I'm
> > > > guessing that one was done manually, but I'd like to try to
> > > > automate it (even if it still requires some manual editing afterwards).
> > > >
> > > > I checked qtrepotools.git but didn't find anything. Simon created
> > > > one, but says that it's not the same one in use by the release team:
> > > >
> > > > http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog
> > >
> > > Replying to myself to say that this tool works really well, and is
> > > very easy to use (especially with
> > > https://codereview.qt-project.org/#/c/253973/). Can the initial
> > > change logs
> > be created with it?
> >
> > We will test this and use it in coming releases if it works better
> > that current one
> 
> For what it's worth, the only negative difference I saw was that it
> (createchangelog) generates this:
> 
> Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
> compatibility (source and binary) with Qt 5.12.1.
> 
> whereas the current one generates this:
> 
> Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
> compatibility (source and binary) with Qt 5.12.0 through 5.12.1.
> 
> Doesn't seem that important though?
> 
> > br,
> > Jani
> >
> > >
> > > > > br,
> > > > > Jani Heikkinen
> > > > > Release Manager
> > > > > ___
> > > > > Development mailing list
> > > > > Development@qt-project.org
> > > > > https://lists.qt-project.org/listinfo/development
> > > > ___
> > > > Development mailing list
> > > > Development@qt-project.org
> > > > https://lists.qt-project.org/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] [Announce] Qt Creator 4.9.0 Beta released

[List for announcements regarding Qt releases and development]

We are happy to announce the release of Qt Creator 4.9 Beta!

https://blog.qt.io/blog/2019/02/21/qt-creator-4-9-beta-released/

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B

___
Announce mailing list
annou...@qt-project.org
https://lists.qt-project.org/listinfo/announce
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Kai Koehne]

Somewhat related: I suggest to stop listening all changes in the commit message 
template. See e.g.

https://codereview.qt-project.org/#/c/253950/

This makes the commit message unnecessarily long, and also means that, if you 
grep though git log history for a specific change, you hit the changelog commit 
too.

I guess the idea was to give anyone working on the change log an idea what 
commit might be worth documenting. Anyhow, it seems not every reviewer removes 
the list before submitting, and frankly speaking it should be easy enough for 
everyone to run e.g. 'git log v5.12.1..5.12.2' themselves.

Kai

> -Original Message-
> From: Development  On Behalf Of
> Cristián Maureira-Fredes
> Sent: Thursday, February 21, 2019 12:47 PM
> To: Mitch Curtis ; Jani Heikkinen ;
> development@qt-project.org
> Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes
> files
> 
> Hello,
> 
> so, we agree the Go one (qtqa) is the recommended one?
> 
> Time ago, I was directed to this one:
> http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-
> tools/create_changelog.pl
> and ended up suggesting this one as a replacement for the Qt for Python
> project: https://codereview.qt-project.org/#/c/252162/
> 
> I understand it is better to focus on one script and improve it so that's why 
> I
> would like to know which is the preferred option.
> 
> Cheers
> 
> 
> From: Development  on behalf of
> Mitch Curtis 
> Sent: 21 February 2019 11:46
> To: Jani Heikkinen; development@qt-project.org
> Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes
> files
> 
> > -Original Message-
> > From: Jani Heikkinen
> > Sent: Thursday, 21 February 2019 11:06 AM
> > To: Mitch Curtis ; development@qt-project.org
> > Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> > > -Original Message-
> > > From: Mitch Curtis 
> > > Sent: torstai 21. helmikuuta 2019 11.21
> > > To: Mitch Curtis ; Jani Heikkinen
> > > ; development@qt-project.org
> > > Subject: RE: [Development] Maintainers, your action needed: Qt
> > > 5.12.2 changes files
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: Development  On Behalf
> > > Of
> > > > Mitch Curtis
> > > > Sent: Thursday, 21 February 2019 9:33 AM
> > > > To: Jani Heikkinen ;
> > > > development@qt-project.org
> > > > Subject: Re: [Development] Maintainers, your action needed: Qt
> > > > 5.12.2 changes files
> > > >
> > > > > -Original Message-
> > > > > From: Development  On
> > Behalf
> > > > Of
> > > > > Jani Heikkinen
> > > > > Sent: Thursday, 21 February 2019 9:19 AM
> > > > > To: development@qt-project.org
> > > > > Subject: [Development] Maintainers, your action needed: Qt
> > > > > 5.12.2 changes files
> > > > >
> > > > > Hi,
> > > > > Initial ones here: https://codereview.qt-
> > > > > project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> > > > >
> > > > > Please take it over, do needed modifications and get '+2' during
> > > > > this
> > > week.
> > > >
> > > > Do we have a script that generates the change logs? I see that
> > > > qtbase has entries for bug fixes with the task number:
> > > >
> > > > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.
> > > > 12
> > > > .1
> > > >
> > > > I'd like to get the same for the modules that I maintain. I'm
> > > > guessing that one was done manually, but I'd like to try to
> > > > automate it (even if it still requires some manual editing afterwards).
> > > >
> > > > I checked qtrepotools.git but didn't find anything. Simon created
> > > > one, but says that it's not the same one in use by the release team:
> > > >
> > > > http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog
> > >
> > > Replying to myself to say that this tool works really well, and is
> > > very easy to use (especially with
> > > https://codereview.qt-project.org/#/c/253973/). Can the initial
> > > change logs
> > be created with it?
> >
> > We will test this and use it in coming releases if it works better
> > that current one
> 
> For what it's worth, the only negative difference I saw was that it
> (createchangelog) generates this:
> 
> Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
> compatibility (source and binary) with Qt 5.12.1.
> 
> whereas the current one generates this:
> 
> Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
> compatibility (source and binary) with Qt 5.12.0 through 5.12.1.
> 
> Doesn't seem that important though?
> 
> > br,
> > Jani
> >
> > >
> > > > > br,
> > > > > Jani Heikkinen
> > > > > Release Manager
> > > > > ___
> > > > > Development mailing list
> > > > > Development@qt-project.org
> > > > > https://lists.qt-project.org/listinfo/development
> > > > ___
> > > > Development mailing list
> > > > Development@qt-project.o

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Cristián Maureira-Fredes]

Hello,

so, we agree the Go one (qtqa) is the recommended one?

Time ago, I was directed to this one: 
http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/create_changelog.pl
and ended up suggesting this one as a replacement for the Qt for Python 
project: https://codereview.qt-project.org/#/c/252162/

I understand it is better to focus on one script and improve it so that's why I 
would like to know
which is the preferred option.

Cheers


From: Development  on behalf of Mitch 
Curtis 
Sent: 21 February 2019 11:46
To: Jani Heikkinen; development@qt-project.org
Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes 
files

> -Original Message-
> From: Jani Heikkinen
> Sent: Thursday, 21 February 2019 11:06 AM
> To: Mitch Curtis ; development@qt-project.org
> Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
>
> > -Original Message-
> > From: Mitch Curtis 
> > Sent: torstai 21. helmikuuta 2019 11.21
> > To: Mitch Curtis ; Jani Heikkinen
> > ; development@qt-project.org
> > Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> >
> >
> > > -Original Message-
> > > From: Development  On Behalf
> > Of
> > > Mitch Curtis
> > > Sent: Thursday, 21 February 2019 9:33 AM
> > > To: Jani Heikkinen ;
> > > development@qt-project.org
> > > Subject: Re: [Development] Maintainers, your action needed: Qt
> > > 5.12.2 changes files
> > >
> > > > -Original Message-
> > > > From: Development  On
> Behalf
> > > Of
> > > > Jani Heikkinen
> > > > Sent: Thursday, 21 February 2019 9:19 AM
> > > > To: development@qt-project.org
> > > > Subject: [Development] Maintainers, your action needed: Qt 5.12.2
> > > > changes files
> > > >
> > > > Hi,
> > > > Initial ones here: https://codereview.qt-
> > > > project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> > > >
> > > > Please take it over, do needed modifications and get '+2' during
> > > > this
> > week.
> > >
> > > Do we have a script that generates the change logs? I see that
> > > qtbase has entries for bug fixes with the task number:
> > >
> > > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.
> > > 12
> > > .1
> > >
> > > I'd like to get the same for the modules that I maintain. I'm
> > > guessing that one was done manually, but I'd like to try to automate
> > > it (even if it still requires some manual editing afterwards).
> > >
> > > I checked qtrepotools.git but didn't find anything. Simon created
> > > one, but says that it's not the same one in use by the release team:
> > >
> > > http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog
> >
> > Replying to myself to say that this tool works really well, and is
> > very easy to use (especially with
> > https://codereview.qt-project.org/#/c/253973/). Can the initial change logs
> be created with it?
>
> We will test this and use it in coming releases if it works better that 
> current
> one

For what it's worth, the only negative difference I saw was that it 
(createchangelog) generates this:

Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.12.1.

whereas the current one generates this:

Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.12.0 through 5.12.1.

Doesn't seem that important though?

> br,
> Jani
>
> >
> > > > br,
> > > > Jani Heikkinen
> > > > Release Manager
> > > > ___
> > > > Development mailing list
> > > > Development@qt-project.org
> > > > https://lists.qt-project.org/listinfo/development
> > > ___
> > > Development mailing list
> > > Development@qt-project.org
> > > https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CMake Workshop Summary

[Kevin Funk]

On Thursday, 21 February 2019 06:58:33 CET Simon Hausmann wrote:
> I tend towards Alexandru’s approach for the sake of a maximal parallel
> build. But it’s not evident yet whether this approach is feasible or
> whether perhaps the external project solution gives better results in terms
> of maintenance / correctness.

Heya,

I agree, I'd first go into the direction Alexandru mentioned.

To be honest, I personally try to stay away from CMake's ExternalProject as 
far as possible these days, having bitten by them badly a couple of times 
already. They just don't feel like they make anything easier, compared to 
running the commands yourself (main issue: you can't easily get a hold of the 
CMake targets created by a subproject in the superbuild; and you usually end 
up reimplementing parts of the CMake config files...). 

So, yep, add_subdirectory() sounds like the way to go; we'll need to check how 
that performs with the amount of existing Qt submodules, though. We might need 
to do a couple more optimizations of the CMake macros/functions in qtbase.git 
for that.

Regards,
Kevin


> With other modules getting wip/cmake branches I can only invite to join,
> experiment with “super builds” and contribute. We also have an irc channel
> on Freenode, #qt-cmake.
 
> Simon
> 
> On 21. Feb 2019, at 00:28, Croitor Alexandru
> mailto:placi...@gmail.com>> wrote:
 
> This is why for Qt For Python, we've opted to make a superproject that
> doesn't use ExternalProejct, but rather uses add_subdirectory on each
> subproject. The advantage is that you can open the superproject
> CMakeLists.txt directly in Qt Creator, and get code completion and all the
> goodies for the whole project. And users can still choose to build each
> subproject separately (or rather that's what the CI does at the moment_.
 I
> don't know whether that would be feasible for qt5 though, given there are a
> lot more subprojects and files and targets. I'm mainly concerned with the
> performance aspect of it. 
> On Wed, Feb 20, 2019 at 10:36 PM Matthew Woehlke
> mailto:mwoehlke.fl...@gmail.com>> wrote:
 On
> 13/02/2019 05.06, Simon Hausmann wrote:
> 
> > We briefly discussed the topic and it's my understanding that an agreement
> > exists to support two types of builds:
>
> >
> >
> > (1) Build a repo, install it, build the next repo, install it, etc.
> > (2) Have a super-project that allows building all of Qt with one call
> > to "cmake", a call to "cmake --build" and finally "$maketool
> > install".
>
> >
> >
> > The latter has not been "developed" yet but I think it's necessary to
> > allow for a convenient transition for the users of Qt.
> 
> For (2), you might want to consider a "superbuild", i.e. a separate
> CMake project that just builds a bunch of external projects¹, each of
> which is a Qt module.
> 
> Some advantages over a simple script or Makefile are that users can
> select what modules they want, and you could probably set it up so that
> users can choose what version of Qt they want to build (e.g. LTS, latest
> release, dev, ...).
> 
> The major disadvantage of "superbuilds" is they tend to be not-great for
> people actually hacking on the code.
> 
> (¹ https://cmake.org/cmake/help/latest/module/ExternalProject.html)
> 
> --
> Matthew
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development


-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Mitch Curtis]

> -Original Message-
> From: Jani Heikkinen
> Sent: Thursday, 21 February 2019 11:06 AM
> To: Mitch Curtis ; development@qt-project.org
> Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
> 
> > -Original Message-
> > From: Mitch Curtis 
> > Sent: torstai 21. helmikuuta 2019 11.21
> > To: Mitch Curtis ; Jani Heikkinen
> > ; development@qt-project.org
> > Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> >
> >
> > > -Original Message-
> > > From: Development  On Behalf
> > Of
> > > Mitch Curtis
> > > Sent: Thursday, 21 February 2019 9:33 AM
> > > To: Jani Heikkinen ;
> > > development@qt-project.org
> > > Subject: Re: [Development] Maintainers, your action needed: Qt
> > > 5.12.2 changes files
> > >
> > > > -Original Message-
> > > > From: Development  On
> Behalf
> > > Of
> > > > Jani Heikkinen
> > > > Sent: Thursday, 21 February 2019 9:19 AM
> > > > To: development@qt-project.org
> > > > Subject: [Development] Maintainers, your action needed: Qt 5.12.2
> > > > changes files
> > > >
> > > > Hi,
> > > > Initial ones here: https://codereview.qt-
> > > > project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> > > >
> > > > Please take it over, do needed modifications and get '+2' during
> > > > this
> > week.
> > >
> > > Do we have a script that generates the change logs? I see that
> > > qtbase has entries for bug fixes with the task number:
> > >
> > > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.
> > > 12
> > > .1
> > >
> > > I'd like to get the same for the modules that I maintain. I'm
> > > guessing that one was done manually, but I'd like to try to automate
> > > it (even if it still requires some manual editing afterwards).
> > >
> > > I checked qtrepotools.git but didn't find anything. Simon created
> > > one, but says that it's not the same one in use by the release team:
> > >
> > > http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog
> >
> > Replying to myself to say that this tool works really well, and is
> > very easy to use (especially with
> > https://codereview.qt-project.org/#/c/253973/). Can the initial change logs
> be created with it?
> 
> We will test this and use it in coming releases if it works better that 
> current
> one

For what it's worth, the only negative difference I saw was that it 
(createchangelog) generates this:

Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.12.1.

whereas the current one generates this:

Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.12.0 through 5.12.1.

Doesn't seem that important though?

> br,
> Jani
> 
> >
> > > > br,
> > > > Jani Heikkinen
> > > > Release Manager
> > > > ___
> > > > Development mailing list
> > > > Development@qt-project.org
> > > > https://lists.qt-project.org/listinfo/development
> > > ___
> > > Development mailing list
> > > Development@qt-project.org
> > > https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Jani Heikkinen]

> -Original Message-
> From: Mitch Curtis 
> Sent: torstai 21. helmikuuta 2019 11.21
> To: Mitch Curtis ; Jani Heikkinen ;
> development@qt-project.org
> Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
> 
> 
> 
> > -Original Message-
> > From: Development  On Behalf
> Of
> > Mitch Curtis
> > Sent: Thursday, 21 February 2019 9:33 AM
> > To: Jani Heikkinen ; development@qt-project.org
> > Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> > > -Original Message-
> > > From: Development  On Behalf
> > Of
> > > Jani Heikkinen
> > > Sent: Thursday, 21 February 2019 9:19 AM
> > > To: development@qt-project.org
> > > Subject: [Development] Maintainers, your action needed: Qt 5.12.2
> > > changes files
> > >
> > > Hi,
> > > Initial ones here: https://codereview.qt-
> > > project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> > >
> > > Please take it over, do needed modifications and get '+2' during this
> week.
> >
> > Do we have a script that generates the change logs? I see that qtbase
> > has entries for bug fixes with the task number:
> >
> > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.12
> > .1
> >
> > I'd like to get the same for the modules that I maintain. I'm guessing
> > that one was done manually, but I'd like to try to automate it (even
> > if it still requires some manual editing afterwards).
> >
> > I checked qtrepotools.git but didn't find anything. Simon created one,
> > but says that it's not the same one in use by the release team:
> >
> > http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog
> 
> Replying to myself to say that this tool works really well, and is very easy 
> to
> use (especially with https://codereview.qt-project.org/#/c/253973/). Can
> the initial change logs be created with it?

We will test this and use it in coming releases if it works better that current 
one

br,
Jani

> 
> > > br,
> > > Jani Heikkinen
> > > Release Manager
> > > ___
> > > Development mailing list
> > > Development@qt-project.org
> > > https://lists.qt-project.org/listinfo/development
> > ___
> > Development mailing list
> > Development@qt-project.org
> > https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Mitch Curtis]

> -Original Message-
> From: Development  On Behalf Of
> Mitch Curtis
> Sent: Thursday, 21 February 2019 9:33 AM
> To: Jani Heikkinen ; development@qt-project.org
> Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
> 
> > -Original Message-
> > From: Development  On Behalf
> Of
> > Jani Heikkinen
> > Sent: Thursday, 21 February 2019 9:19 AM
> > To: development@qt-project.org
> > Subject: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> > Hi,
> > Initial ones here: https://codereview.qt-
> > project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> >
> > Please take it over, do needed modifications and get '+2' during this week.
> 
> Do we have a script that generates the change logs? I see that qtbase has
> entries for bug fixes with the task number:
> 
> http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.12.1
> 
> I'd like to get the same for the modules that I maintain. I'm guessing that 
> one
> was done manually, but I'd like to try to automate it (even if it still 
> requires
> some manual editing afterwards).
> 
> I checked qtrepotools.git but didn't find anything. Simon created one, but
> says that it's not the same one in use by the release team:
> 
> http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog

Replying to myself to say that this tool works really well, and is very easy to 
use (especially with https://codereview.qt-project.org/#/c/253973/). Can the 
initial change logs be created with it?

> > br,
> > Jani Heikkinen
> > Release Manager
> > ___
> > Development mailing list
> > Development@qt-project.org
> > https://lists.qt-project.org/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Mitch Curtis]

> -Original Message-
> From: Development  On Behalf Of
> Jani Heikkinen
> Sent: Thursday, 21 February 2019 9:19 AM
> To: development@qt-project.org
> Subject: [Development] Maintainers, your action needed: Qt 5.12.2 changes
> files
> 
> Hi,
> Initial ones here: https://codereview.qt-
> project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> 
> Please take it over, do needed modifications and get '+2' during this week.

Do we have a script that generates the change logs? I see that qtbase has 
entries for bug fixes with the task number:

http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.12.1

I'd like to get the same for the modules that I maintain. I'm guessing that one 
was done manually, but I'd like to try to automate it (even if it still 
requires some manual editing afterwards).

I checked qtrepotools.git but didn't find anything. Simon created one, but says 
that it's not the same one in use by the release team:

http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog

> br,
> Jani Heikkinen
> Release Manager
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Jani Heikkinen]

Hi,
Initial ones here: 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z

Please take it over, do needed modifications and get '+2' during this week.

br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development