[Development] Qt 6.0.x releasing and Qt 6.0.x changes files

[Jani Heikkinen]

Hi,

Lars made a new proposal, see his comment in https://codereview.qt-project.org/c/qt/qtbase/+/324440

Basic idea would be
   * We will create one release note for the release instead of separate changes file in each submodule
   * Release notes are stored in separate release notes git repository. That way we can freeze Qt release content & generate ( and finalize) release notes after the content freeze
   * We will remove dist/ folder in our current repos

All that would be doable also in Qt 6.0.1 schedule (except of fully automated release note generation but that can be solved independently later) so at least I will support this Lars proposal. Any comments?

br,
Jani  Heikkinen

> -----Original Message-----
> From: Development <development-bounces at qt-project.org> On Behalf Of
> Jani Heikkinen
> Sent: tiistai 1. joulukuuta 2020 11.01
> To: development at qt-project.org
> Subject: [Development] Qt 6.0.x releasing and Qt 6.0.x changes files
> 
> Hi all,
> 
> Qt 6.0.0 should be out really soon and it is time to start planning upcoming
> patch level releases for the Qt 6.0 series. Plan is to release quick updates for
> the Qt 6.0 pretty much similarly than we did in the beta phase. It means
> there should be a new Qt 6.0.x patch release once / 2-3 weeks. That way we
> could get regular updates to the users & releasing should be quite easy due
> to the limited set of changes. We could even do these patch releases directly
> from the '6.0' branch if we want...
> 
> But how to create changes files for the modules with this process? If we
> need to freeze the release content, generate initial changes files, finalize
> those, review, integrate, etc this new process won't work; it just takes a too
> long time to complete. So we need to get those changes files in the packages
> automatically or just stop updating those in the git and attach those in the
> release some other way.
> 
> Would it be ok to add a general Qt 6.0.x changes file in each module
> (something like this: https://codereview.qt-
> project.org/c/qt/qtbase/+/324440 ) and also add a pure change list in the
> wiki? That would be a lightweight process & makes regular, quick patch level
> releases possible.
> 
> Thoughts?
> 
> Br,
> Jani Heikkinen
> Release Manager
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development