Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files
Hi all, Please finalize changes files now; It would be really weird to delay the release because of missing changes file... br, Jani From: Development on behalf of Jani Heikkinen Sent: Thursday, February 21, 2019 10: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. 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
Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files
> -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
> 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
> -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
Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files
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 w
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.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
> -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
> -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
> -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
> -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
