Reproog/novelWriter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Properly update release notes

Browse Source
This commit is contained in:
Veronica K. B. Olsen
2021-03-13 16:54:02 +01:00
parent 612ec06262
commit 32bcb52f14
2 changed files with 18 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+8 -5
View File
@@ -4,13 +4,16 @@
### Release Notes ### Release Notes
This is the release candidate of 1.2. The release is intended for testing of new features and to This release is mainly focused on the Build Novel Project tool. Completely new export classes have
sort out potential bugs before the full release. Please take this into account when working on your been written to support Open Document and Markdown exports. In addition, the way document layouts
live projects. are handled have been automated a little to assist the user in keeping header levels and document
layout flags in sync. The third new additoion is the ability to record and log idle time during a
writing session to improve the writing statistics information as requested by several users.
Finally, it is now possible to directly edit the project dictionary via a new, simple GUI dialog.
#### The Build Novel Project Tool #### The Build Novel Project Tool
The main changes for version 1.2 are to the Build Novel Project tool. The Open Document export, as The main changes for this release are to the Build Novel Project tool. The Open Document export, as
well as the Markdown export, is now handled entirely by code written for novelWriter. Previously, well as the Markdown export, is now handled entirely by code written for novelWriter. Previously,
these export features depended on the underlying Qt library's save routines connected to the these export features depended on the underlying Qt library's save routines connected to the
preview document shown in the build dialog. Using this method of export both meant that the content preview document shown in the build dialog. Using this method of export both meant that the content
@@ -104,7 +107,7 @@ _These Release Notes also include the changes from 1.2 Beta 1 and RC 1._
**Documentation** **Documentation**
* The documentation has been updated to reflect the changes in 1.2, and a few corrections pointed * The documentation has been updated to reflect the changes in 1.2, and a few corrections pointed
out by @jyhelle fixed. PR #700. out by @jyhelle applied. PR #700.
---- ----
nw/assets/text/release_notes.htm
+10 -6
View File
@@ -2,14 +2,18 @@
<html> <html>
<body> <body>
<h2>Release Notes for 1.2 RC 1</h2> <h2>Release Notes for 1.2</h2>
<p><i>Released on 2 March 2021</i></p> <p><i>Released on 14 March 2021</i></p>
<p>This is the release candidate of 1.2. The release is intended for testing of new features and to <p>This release is mainly focused on the Build Novel Project tool. Completely new export classes
sort out potential bugs before the full release. Please take this into account when working on your have been written to support Open Document and Markdown exports. In addition, the way document
live projects.</p> layouts are handled have been automated a little to assist the user in keeping header levels and
document layout flags in sync. The third new additoion is the ability to record and log idle time
during a writing session to improve the writing statistics information as requested by several
users. Finally, it is now possible to directly edit the project dictionary via a new, simple GUI
dialog.</p>
<h3>The Build Novel Project Tool</h3> <h3>The Build Novel Project Tool</h3>
<p>The main changes for version 1.2 are to the Build Novel Project tool. The Open Document export, <p>The main changes for this release are to the Build Novel Project tool. The Open Document export,
as well as the Markdown export, is now handled entirely by code written for novelWriter. as well as the Markdown export, is now handled entirely by code written for novelWriter.
Previously, these export features depended on the underlying Qt library's save routines connected Previously, these export features depended on the underlying Qt library's save routines connected
to the preview document shown in the build dialog. Using this method of export both meant that the to the preview document shown in the build dialog. Using this method of export both meant that the