Release notes XLT 10 (#307)

* Release notes XLT 10

* fixes

* Apply suggestions from code review

Co-authored-by: h-arlt <4641065+h-arlt@users.noreply.github.com>

---------

Co-authored-by: Joerg Werner <j.werner@xceptance.de>
Co-authored-by: h-arlt <4641065+h-arlt@users.noreply.github.com>

Author: 3 people

content/en/xlt/release-notes/10_0_x.md

@@ -17,4 +17,75 @@ sitemap:
 
 ## XLT 10.0.0-beta-1
 
-*Work in progress. Please check back later.*
+Version 10 is a major release of XLT. It comes with new features, but also some incompatible changes. See below for an overview of what's in the box.
+
+You may need to migrate your test suites for use with this new version. Please read the *Test Suite Migration* section carefully.
+
+
+### Overview
+
+#### Load Testing
+
+XLT now uses *virtual threads* to execute load testing scenarios. Virtual threads, a feature of Java 21, are a much lighter alternative to platform threads. They enable test suite designers to create highly concurrent test suites with up to a hundred thousand parallel activities on a single machine, which is typically not possible with regular platform threads.
+
+There is no change to the programming model. The developer-friendly one-thread-per-activity approach remains the same.
+
+Virtual threads are enabled by default. To use platform threads instead, turn off virtual threads in the configuration of your test suite:
+
+```properties
+com.xceptance.xlt.virtualThreads.enabled = false
+```
+
+Note that virtual threads do not make the underlying machine "faster". They simply allow for higher concurrency with the same set of resources. Therefore, ensure that the machine matches your intended load profile.
+
+
+#### Load Test Report
+
+##### Dynamic Charts
+
+The *Dynamic Overview* charts have been improved. They now display data in the report's time zone, not just in UTC. Additionally, the gray minimum-maximum band remains intact when zooming in. Finally, the tooltip now shows the _count/s_ value as well.
+
+##### Moving Averages
+
+The *Averages* chart can now include additional moving averages alongside the standard moving average. The look-behind window used to calculate a moving average can now be defined not only by a percentage of previous values, but also by a time range. Additionally, moving average series lines now start already at the first data point in the chart rather than after the first complete look-behind window.
+
+The report generator now creates three moving averages by default. The 5% standard moving average known from previous reports is now accompanied by 2% and 10% moving averages.
+
+The configuration of moving averages in the `<xlt>/config/reportgenerator.properties` file has been adjusted to accommodate these changes. See below for an example:
+
+```properties
+## The standard moving average with a window of 5% of the values.
+com.xceptance.xlt.reportgenerator.charts.commonAverage.type = percentage
+com.xceptance.xlt.reportgenerator.charts.commonAverage.value = 5%
+
+## An additional moving average with a window of 10% of the values.
+com.xceptance.xlt.reportgenerator.charts.averages.1.type = percentage
+com.xceptance.xlt.reportgenerator.charts.averages.1.value = 10%
+
+## An additional moving average with a window of 10 minutes.
+com.xceptance.xlt.reportgenerator.charts.averages.2.type = time
+com.xceptance.xlt.reportgenerator.charts.averages.2.value = 10m
+```
+
+
+### Test Suite Migration
+
+As mentioned above, XLT 10 includes breaking changes. In order to migrate your test suites and their associated libraries, you must complete the following steps.
+
+#### 1. Fix Compile Errors
+
+Due to new features and code cleanups, there may be incompatible API changes. Typical test suites are not affected by these changes, but yours may be. Adjust your code accordingly.
+
+* The `XltFirefoxDriver.Builder` no longer offers to set the `FirefoxProfile` object and the (deprecated) `FirefoxBinary` object, but instead offers to set a `FirefoxOptions` object. You can set the profile and the path to the Firefox binary on that `FirefoxOptions` object.
+
+* The `ReportProviderConfiguration` interface no longer provides the `int getMovingAveragePercentage()` method. Instead, it offers these two alternative methods:
+    * `MovingAverageConfiguration getCommonMovingAverageConfig()`
+    * `List<MovingAverageConfiguration> getAdditionalMovingAverageConfigs()`
+
+#### 2. Test Your Scenarios
+
+Now it's time to verify that everything still works as it did before. Start by running the test scenarios from your IDE. They should run and produce the expected results. Then run a small load test. Check the results and the output in all log files.
+
+#### 3. Review the Report Generator Configuration
+
+As mentioned above, the XLT report generator can now create additional moving averages. You can configure them in the `<xlt>/config/reportgenerator.properties` file. Check the defaults to see if they work for you and adjust them as needed.

content/en/xtc/xtc-release-notes/v110.md

@@ -21,7 +21,7 @@ sitemap:
 * XTC now provides an additional XLT execution environment **10.x**. In this environment, a preview of XLT 10 is installed for field testing the support for virtual threads. Use with caution.
 * Currently available XLT execution environments:
     * XLT 9.x → [9.2.2]({{< relref "/xlt/release-notes/9_2_x" >}}) (recommended)
-    * XLT 10.x → [10.0.0-beta-1]({{< relref "/xlt/release-notes/10_0_x" >}})
+    * XLT 10.x → [10.0.0-beta-1]({{< relref "/xlt/release-notes/10_0_x" >}}) (**[migration needed]({{< relref "/xlt/release-notes/10_0_x#test-suite-migration" >}})**)
 
 
 ## Platform