Merge pull request #1199 from jenriquesoriano/master

Release strategy 2025 update. Readme and diagram updated with new date (09/07/2025)

Author: jenriquesoriano

release strategy/README.md

@@ -4,7 +4,7 @@
 - [Release Planning](#release-planning)
   * [Instances of the INSPIRE Reference Validator](#instances-of-the-inspire-reference-validator)
   * [Annual releases](#annual-releases)
-    * [v2025.1 - 15/06/2025](#v20251---15062025)
+    * [v2025.1 - 09/07/2025](#v20251---09072025)
 - [Release Delivery](#release-delivery)
 
 # Introduction
@@ -35,10 +35,10 @@ As mentioned above, as of 2025 a single release of the INSPIRE Reference Validat
 
 For simplicity, the descriptions make explicit reference to the release in the year 2025, but the same release schedule will be applied consistently over the following years:
 
-* **v2025.1 - 15/06/2025**: it includes both breaking and non-breaking changes. This release is the one used for the end-of-year Monitoring process.
+* **v2025.1 - 09/07/2025**: it includes both breaking and non-breaking changes. This release is the one used for the end-of-year Monitoring process.
 
-### v2025.1 - 15/06/2025
-This release is scheduled on 15/06/2025 and includes the breaking and non-breaking changes occurred since the previous release (v2024.3). All these changes (each managed in a dedicated branch) are first incorporated in the _staging_ branch, i.e. they are made available in the Staging instance; afterwards, each change which is also tested and accepted by the user who originally reported it, is also incorporated in the _v2025.1_ branch. This branch is finally merged into the _master_ branch, which will make all changes available in the Production instance. Should hotfixes be needed at any time, they are immediately incorporated both in the _staging_ and the _master_ branches.
+### v2025.1 - 09/07/2025
+This release is scheduled on 09/07/2025 and includes the breaking and non-breaking changes occurred since the previous release (v2024.3). All these changes (each managed in a dedicated branch) are first incorporated in the _staging_ branch, i.e. they are made available in the Staging instance; afterwards, each change which is also tested and accepted by the user who originally reported it, is also incorporated in the _v2025.1_ branch. This branch is finally merged into the _master_ branch, which will make all changes available in the Production instance. Should hotfixes be needed at any time, they are immediately incorporated both in the _staging_ and the _master_ branches.
 ![v2025.1](./img/v2025.1.png "v2025.1")
 
 # Release Delivery