updated the road map for 3.0.0-M5 and next versions
diff --git a/maven-surefire-plugin/src/site/apt/index.apt.vm b/maven-surefire-plugin/src/site/apt/index.apt.vm
index 58d5750..b895c39 100644
--- a/maven-surefire-plugin/src/site/apt/index.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/index.apt.vm
@@ -79,28 +79,31 @@
*---------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | Test Report tasks (prerequisite: SUREFIRE-1222 in 3.0.0-M4) \ |
| | New interprocess communication with TCP/IP which fixed current blocker and critical bugs. \ |
-| | Provided extensions which can be used to customize this interprocess communication in plugin configuration. It is internally used to switch over the pipes and TCP connector. \ |
-| | (1) We will identify the test by UniqueId in SimpleReportEntry and not by the traditional combination of class/method name. (ready for parameterized tests and a coherent re-run) \ |
-| | (2) TestSetRunListener should not cache test event and make any guess about the impl in StatelessXmlReporter. TestSetRunListener should only forward events to multiple reporters.\ |
-| 3.0.0-M5 | (3) Fire and consume more events (normal run start/end, re-run start/end) \ |
-| | (4) StatelessXmlReporter repeatedly generates XML report. It is stateful report and won't work if re-run or parallel executions send test events out of order. Prerequisite: 1-3 \ |
+| 3.0.0-M5 | Provided extensions which can be used to customize this interprocess communication in plugin configuration. It is internally used to switch over the pipes and TCP connector. \ |
| | \ |
| | {{{https://issues.apache.org/jira/browse/SUREFIRE-1658}TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication.}} \ |
+*---------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | (1) We will identify the test by UniqueId in SimpleReportEntry and not by the traditional combination of class/method name. (ready for parameterized tests and a coherent re-run) \ |
+| | (2) TestSetRunListener should not cache test event and make any guess about the impl in StatelessXmlReporter. TestSetRunListener should only forward events to multiple reporters.\ |
+| | (3) Fire and consume more events (normal run start/end, re-run start/end) \ |
+| 3.0.0-M6 | (4) StatelessXmlReporter repeatedly generates XML report. It is stateful report and won't work if re-run or parallel executions send test events out of order. Prerequisite: 1-3 \ |
+| | \ |
+| | {{{https://issues.apache.org/jira/browse/SUREFIRE-1643}JUnit 5 in parallel execution mode confuses Surefire reports}} \ |
| | {{{https://issues.apache.org/jira/browse/SUREFIRE-1661}ConsoleOutputFileReporter should support parallel execution of test-sets}} \ |
*---------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| | Providers implementation and API \ |
| | More test events used to negotiate tests to run on particular fork JVM. It is useful in situations when the tests are filtered by group/category or classpath scan with file \ |
-| 3.0.0-M6 | filter (fork JVM is preferable over Maven JVM) and used in Test List Processor (3.0.0-M7). We will keep IsolatedClassLoader for extension 'Test List Processor' so that the user \ |
-| | can decide the JVM where the tests will be searched. Possibly JUnit5 provider will be able to scan classes by annotations, see launcher.discover(), and negotiate over the forks. \ | \ |
+| 3.0.0-M7 | filter (fork JVM is preferable over Maven JVM) and used in Test List Processor (3.0.0-M8). We will keep IsolatedClassLoader for extension 'Test List Processor' so that the user \ |
+| | can decide the JVM where the tests will be searched. Possibly JUnit5 provider will be able to scan classes by annotations, see launcher.discover(), and negotiate over the forks. \ |
| | \ |
| | {{{https://issues.apache.org/jira/browse/SUREFIRE-1535}Surefire unable to run testng suites in parallel}} \ |
*---------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| | Extensions API to customize test-set with test list processor (prerequisite: 3.0.0-M6) \ |
-| 3.0.0-M7 | (possibly the scan of classpath based on annotations, currently the scan is done based on pattern of file name e.g. -Dtest=MyTest) \ |
+| | Extensions API to customize test-set with test list processor (prerequisite: 3.0.0-M7) \ |
+| 3.0.0-M8 | (possibly the scan of classpath based on annotations, currently the scan is done based on pattern of file name e.g. -Dtest=MyTest) \ |
| | \ |
| | {{{https://issues.apache.org/jira/browse/SUREFIRE-726}Test list preprocessor support for tests to be run}} \ |
*---------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| 3.0.0-M8 | Breaking backwards compatibility with system properties in configuration parameters, removing deprecated configuration parameters and removing deprecated code, etc. \ |
+| 3.0.0-M9 | Breaking backwards compatibility with system properties in configuration parameters, removing deprecated configuration parameters and removing deprecated code, etc. \ |
*---------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
#{if}(${project.artifactId}=="maven-surefire-plugin")
