Loading...

XML

Word

Printable

We will stop using module specific changes files & start publishing combined release notes for the releases (see https://lists.qt-project.org/pipermail/development/2020-December/040792.html)

relates to

QTQAINFRA-3390 Render markdown files in html instead of showing raw source on code.qt.io

1.	Create a script to generate initial release note	Closed	Antti Kokko
2.	Create a way to publish release notes	Closed	Jani Heikkinen
3.	Delete /dist folders from submodules	Closed	Jani Heikkinen
4.	Add description for fixed bugs	Closed	Antti Kokko
5.	Include changes containing 'Task-number:' in the release note#bug fixes	Closed	Antti Kokko
6.	Add 72 columns wrapping	Closed	Antti Kokko
7.	Use markdown format in release notes	Closed	Antti Kokko
8.	Add known issues section in the initial note	Closed	Antti Kokko

For Gerrit Dashboard: QTBUG-90232
#	Subject	Branch	Project	Status	CR	V
340319,3	generate_release_note.py: Include report summary for fixed bugs	master	qtsdk/tqtc-qtsdk	Status: MERGED	+2	0
341178,6	generate_release_note.py: Add 'Task-number' items and Jira summaries	master	qtsdk/tqtc-qtsdk	Status: MERGED	+2	0
347970,2	generate_release_note.py: Follow 72 column line-wrap convention	master	qtsdk/tqtc-qtsdk	Status: MERGED	+2	0
349714,5	generate_release_note.py: Use markdown syntax	master	qtsdk/tqtc-qtsdk	Status: MERGED	+2	0
350972,2	generate_release_note.py: Add 'Known Issues' section	master	qtsdk/tqtc-qtsdk	Status: MERGED	+2	0

There are no open Gerrit changes