Write release-note and user-guide

Issue: #2229
Signed-off-by: yongjunhong <[email protected]>

Author: YongGoose

documentation/src/docs/asciidoc/release-notes/release-notes-5.12.0-M1.adoc

@@ -155,4 +155,11 @@ JUnit repository on GitHub.
 [[release-notes-5.12.0-M1-junit-vintage-new-features-and-improvements]]
 ==== New Features and Improvements
 
-* ❓
+* Introduced support for parallel execution in the JUnit Vintage engine.
+- Added the `junit.vintage.execution.parallel.enabled` property to enable or disable parallel execution.
+  Defaults to `false`.
+- Added the `junit.vintage.execution.parallel.pool-size` property to configure the size of the thread pool used for
+  parallel execution. Defaults to the number of available processors.
+- Enhanced the `VintageTestEngine` to respect these properties and execute tests in parallel when enabled.
+- Improved test execution performance by allowing multiple tests to run concurrently, reducing overall
+  test suite execution time.

documentation/src/docs/asciidoc/user-guide/migration-from-junit4.adoc

@@ -36,6 +36,29 @@ annotated with `@Category(Example.class)`, it will be tagged with `"com.acme.Exa
 Similar to the `Categories` runner in JUnit 4, this information can be used to filter the
 discovered tests before executing them (see <<running-tests>> for details).
 
+[[migrating-from-junit4-parallel-execution]]
+=== Parallel Execution Support in JUnit Vintage
+
+JUnit Vintage now supports parallel execution of tests, allowing existing JUnit 3 and
+JUnit 4 tests to benefit from improved performance through concurrent test execution.
+
+To enable parallel execution, set the `junit.vintage.execution.parallel.enabled` property
+to `true`. By default, this property is set to `false`.
+
+You can also configure the size of the thread pool used for parallel execution by setting
+the `junit.vintage.execution.parallel.pool-size` property. By default, this property is
+set to the number of available processors.
+
+Example configuration in `junit-platform.properties`:
+
+[source,properties]
+----
+junit.vintage.execution.parallel.enabled=true
+junit.vintage.execution.parallel.pool-size=4
+----
+
+With these properties set, the `VintageTestEngine` will execute tests in parallel,
+significantly reducing the overall test suite execution time.
 
 [[migrating-from-junit4-tips]]
 === Migration Tips

junit-vintage-engine/src/main/java/org/junit/vintage/engine/VintageTestEngine.java

@@ -11,7 +11,6 @@
 package org.junit.vintage.engine;
 
 import static org.apiguardian.api.API.Status.INTERNAL;
-import static org.apiguardian.api.API.Status.STABLE;
 import static org.junit.platform.engine.TestExecutionResult.successful;
 import static org.junit.vintage.engine.descriptor.VintageTestDescriptor.ENGINE_ID;
 
@@ -61,7 +60,7 @@ public final class VintageTestEngine implements TestEngine {
 	 *
 	 * @since 5.12
 	 */
-	@API(status = STABLE, since = "5.12")
+	@API(status = INTERNAL, since = "5.12")
 	public static final String PARALLEL_EXECUTION_ENABLED = "junit.vintage.execution.parallel.enabled";
 
 	/**
@@ -73,7 +72,7 @@ public final class VintageTestEngine implements TestEngine {
 	 *
 	 * @since 5.12
 	 */
-	@API(status = STABLE, since = "5.12")
+	@API(status = INTERNAL, since = "5.12")
 	public static final String PARALLEL_POOL_SIZE = "junit.vintage.execution.parallel.pool-size";
 
 	@Override