[GitHub] [maven-surefire] Tibor17 edited a comment on issue #251: roadmap chart

[GitBox <gi...@apache.org>]

Tibor17 edited a comment on issue #251: roadmap chart
URL: https://github.com/apache/maven-surefire/pull/251#issuecomment-549587369
 
 
   > 
   > 
   > @Tibor17
   > is it really necessary to publish such roadmap?
   
   Maybe it is important for contributors/devs because some people at the U.S. Universities found Surefire as an interesting project and they started similar activities by themselves that we have in this plan too. And it was a perfect match because we left their activity with Shell scripting and started contributing to Surefire because our plan really targets their research problem at the University.
   
   So now the contributors can see if they fit, and if not then we can include them.
   
   Our goal with @krosenvold @agudian is to put the `extensions` in Test List Processor and break backwards compatibility with system properties of config parameters (means added prefix: `surefire.` and `failsafe.`).
   If you know these three things, as the Surefire internals (code and req extentions) and user req (like `-Dtest=org.asf.MyTest` over `-Dtest=org/asf/MyTest.java`) and the path of JUnit5, then you must see that our internal code and documentation should change (more inside and less outside) and this is possible only in major version.
   With this plan we do not break anything till the end and we satisfy our internal req and users too.
   Therefore this is on GH because the dvelopers can immediately see what changed in the history of road map and what code changed for the road map.
   I do not see ML as a benefit in this special case because our contrinutors notice usually the most recent email in ML and not the diff.
   
   > We can have JIRAs and assign them to a version.
   
   I want to have this work done in Jira of course but we need to find the time slot to do it.
   Maybe you would help if you like to.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services