Prepares code for version 2.10.0.

HugoFara · Apr 1, 2024 · 58f3a03 · 58f3a03
1 parent 10b9c2b
commit 58f3a03
Show file tree

Hide file tree

Showing 4 changed files with 20 additions and 10 deletions.
diff --git a/Doxyfile b/Doxyfile
@@ -48,7 +48,7 @@ PROJECT_NAME           = "Learning with Texts - Fork"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 2.9.1-fork
+PROJECT_NUMBER         = 2.10.0-fork
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md
@@ -5,7 +5,7 @@ other versions come from the canonical LWT ("official" branch on Git).
 For git tags, official releases are marked like "v1.0.0", while unofficial
 ones are marked like "v1.0.0-fork".
 
-## [Unreleased]
+## [2.10.0-fork] (April 1 2024)
 
 ### Added
 
@@ -100,12 +100,12 @@ Solves [#129](https://github.com/HugoFara/lwt/issues/129), thanks to the help of
   multi-word on multiple texts was displaying it at many positions on creation.
 * Japanese:
   * Parsing Japanese texts with MeCab was creating warnings when the text was not
-  finishing by a punctation mark.
+  finishing by a punctuation mark.
   * Multi-words were not saved with MeCab parsing on Japanese.
   * Japanese was always requiring MeCab for TTS, even if it was not used
   ([#155](https://github.com/HugoFara/lwt/pull/155)) and [#182](https://github.com/HugoFara/lwt/pull/182).
 * On word review (test):
-  * Space keyboard shortcut may have been inoperating.
+  * Space keyboard shortcut may have been inoperative.
   * On `api.php`, tests were always set to "multi-word" due to a missing variable
   type conversion. Pull request [#175](https://github.com/HugoFara/lwt/pull/175).
   * Text-To-Speech was not working (suggested by [#187](https://github.com/HugoFara/lwt/pull/187)).
@@ -130,6 +130,10 @@ resulting in failed installation the first time.
 * New text creation workflow simplified in `inc/database_connect.php`: `update_default_values` replaced by
 `registerSentencesTextItems` and `check_text` by `displayTextStatistics`.
 
+### Full Changelog for 2.10.0-fork
+
+* [2.9.1...2.10.0](https://github.com/HugoFara/lwt/compare/2.9.1...2.10.0)
+
 ## 2.9.1-fork (December 29 2023)
 
 ### Added in 2.9.1-fork

diff --git a/docs/info.html b/docs/info.html
@@ -234,7 +234,7 @@ <h2 name="current" id="current">
 			</h2>
 
 			<p>
-				The current version is 2.10.0-fork (December 29 2023).
+				The current version is 2.10.0-fork (April 01 2024).
 				<br>
 				<a href="#CHANGELOG">View the Changelog.</a>
 			</p>
@@ -1696,7 +1696,7 @@ <h3>New version</h3>
 <p>The steps to publish a new version are:</p>
 <ol>
 <li>In the <a href="./CHANGELOG.md">CHANGELOG</a>, add the latest release number and date.</li>
-<li>Update <code>get_version</code> in <code>inc/kernel_utility.php</code> with the release number and date.</li>
+<li>In <code>inc/kernel_utility.php</code>, update <code>LWT_APP_VERSION</code> and <code>LWT_RELEASE_DATE</code>.</li>
 <li>Update <code>PROJECT_NUMBER</code> in <code>Doxyfile</code> to the latest release number.</li>
 <li>Regenerate documentation with <code>composer doc</code>.</li>
 <li>Commit your changes, <code>git commit -m "Regenerates documentation for release []."</code>
@@ -2230,7 +2230,7 @@ <h2 id="CHANGELOG" name="CHANGELOG">▶ Changelog - <a href="#">[↑]</a></h2>
 other versions come from the canonical LWT ("official" branch on Git).
 For git tags, official releases are marked like "v1.0.0", while unofficial
 ones are marked like "v1.0.0-fork".</p>
-<h3>[Unreleased]</h3>
+<h3>[2.10.0-fork] (April 1 2024)</h3>
 <h4>Added</h4>
 <ul>
 <li>Support for Japanese with MeCab on Mac! This was added thanks to
@@ -2360,15 +2360,15 @@ <h4>Fixed</h4>
 <li>Japanese:
 <ul>
 <li>Parsing Japanese texts with MeCab was creating warnings when the text was not
-finishing by a punctation mark.</li>
+finishing by a punctuation mark.</li>
 <li>Multi-words were not saved with MeCab parsing on Japanese.</li>
 <li>Japanese was always requiring MeCab for TTS, even if it was not used
 (<a href="https://github.com/HugoFara/lwt/pull/155">#155</a>) and <a href="https://github.com/HugoFara/lwt/pull/182">#182</a>.</li>
 </ul>
 </li>
 <li>On word review (test):
 <ul>
-<li>Space keyboard shortcut may have been inoperating.</li>
+<li>Space keyboard shortcut may have been inoperative.</li>
 <li>On <code>api.php</code>, tests were always set to "multi-word" due to a missing variable
 type conversion. Pull request <a href="https://github.com/HugoFara/lwt/pull/175">#175</a>.</li>
 <li>Text-To-Speech was not working (suggested by <a href="https://github.com/HugoFara/lwt/pull/187">#187</a>).</li>
@@ -2396,6 +2396,12 @@ <h4>Deprecated</h4>
 <li>New text creation workflow simplified in <code>inc/database_connect.php</code>: <code>update_default_values</code> replaced by
 <code>registerSentencesTextItems</code> and <code>check_text</code> by <code>displayTextStatistics</code>.</li>
 </ul>
+<h4>Full Changelog for 2.10.0-fork</h4>
+<ul>
+<li>
+<a href="https://github.com/HugoFara/lwt/compare/2.9.1...2.10.0">2.9.1...2.10.0</a>
+</li>
+</ul>
 <h3>2.9.1-fork (December 29 2023)</h3>
 <h4>Added in 2.9.1-fork</h4>
 <ul>

diff --git a/inc/kernel_utility.php b/inc/kernel_utility.php
@@ -22,7 +22,7 @@
  /**
   * @var string Date of the lastest published release of LWT 
   */
- define('LWT_RELEASE_DATE', "2023-12-29");
+ define('LWT_RELEASE_DATE', "2024-04-01");
 
 /**
  * Return LWT version for humans