Hi Using slack is a good idea for discussion. But bear mind @ASF all decisions must appear on a mailing list or in a jira ticket. Interesting blog entry regarding this topic "If it didn’t happen on the mailing list, it didn’t happen." http://theapacheway.com/on-list/ think about timezone or people availability and btw this slack is only for @apache user etc...
On Wed, 27 Feb 2019 at 04:01, Tibor Digana <[email protected]> wrote: > Stephane, > I have been quite busy with other JUnit5 work - SUREFIRE-1585. > Can you join us in the chat on Slack "the-asf.slack.com"? > You will find the Channel named "surefire". > Ping us as soon as you are ready and we will find some way. > I am glad! > > Cheers > Tibor > > On Mon, Feb 25, 2019 at 8:54 AM Stephane Nicoll <[email protected] > > > wrote: > > > Hi everyone, > > > > It's great to see the progress on Surefire 3.0 and I wanted to reach out > to > > discuss a practicable problem with the 2.x line. There are a number of > > fixes for JUnit 5 that are only available in the 3.x line that isn't GA > > yet. [1][2] > > > > Putting my Spring Boot hat for a min, this actually prevents us from > > upgrading our test support to JUnit 5: our plan is to offer maximum > > flexibility by providing the vintage engine (so that users can keep their > > tests and migrate at their own pace). > > > > We can't upgrade to a milestone as our upgrade policy prevents that > > (regardless of how stable this is and especially since backward > > incompatible changes have been pushed to the latest milestone). So we're > > kind of stuck. > > > > Would there be an appetite to backport those fixes and release a 2.22.2? > > > > Thanks, > > S. > > > > [1] https://issues.apache.org/jira/browse/SUREFIRE-1614 > > [2] > https://issues.apache.org/jira/projects/SUREFIRE/issues/SUREFIRE-1546 > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
