Releasing 2.3.1 of surefire plugin

I pinged the devs as listed on the JIRA site and Brett
suggested I
join this list.

My original request was:

There are a large number of people waiting for
http://j
ira.codehaus.org/browse/SUREFIRE-257 temporary fix of
providing surefire-report:report-only.

I've been contemplating cutting a release for it for some
time, but I
am not sure how I would go about this since the plugin is in
the same
project as surefire itself.

If you have no problems with releasing a 2.3.?? of the
plugin only and
are willing to sketch out the basics of how you would like
that done,
then I can do the work and get you to validate what I have
done.


And Brett mentioned there were some things to check on
Windows, so if
you want list them out I can have a look.

Hi Barrie,

No need to release the plugin independantly - we should do a
full  
surefire release. The branch for 2.3.1 already exists.

We just have 4 issues to resolve before it shold be
released: http:// 
jira.codehaus.org/secure/IssueNavigator.jspa? 
reset=true&mode=hide&sorter/order=DESC&sorter/ 
field=priority&resolution=-1&pid=10541&fixfor=13
251

One of them, 297, was the one that needed windows testing.
Dennis and  
I looked at it at ApacheCon. I think, if you see my comment,
that  
basically the behaviour is now consistent across versions
and we just  
need to document that only certain styles of quoting of
arguments  
work. You probably understand the problem there already. The
key  
thing is that testing needs to occur both across surefire
versions  
(2.2, 2.3 which supposedly regressed, and 2.3.1-SNAPSHOT)
and maven  
versions (2.0.5 and 2.0.6, since 2.0.6 changed the behaviour
of  
plexus-utils in plugins).

Does that make sense?

- Brett

On 18/05/2007, at 7:40 AM, Barrie Treloar wrote:

> I pinged the devs as listed on the JIRA site and Brett
suggested I
> join this list.
>
> My original request was:
>
> There are a large number of people waiting for
> http://j
ira.codehaus.org/browse/SUREFIRE-257 temporary fix of
> providing surefire-report:report-only.
>
> I've been contemplating cutting a release for it for
some time, but I
> am not sure how I would go about this since the plugin
is in the same
> project as surefire itself.
>
> If you have no problems with releasing a 2.3.?? of the
plugin only and
> are willing to sketch out the basics of how you would
like that done,
> then I can do the work and get you to validate what I
have done.
>
>
> And Brett mentioned there were some things to check on
Windows, so if
> you want list them out I can have a look.

On 5/21/07, Brett Porter <brettapache.org> wrote:
> Hi Barrie,
>
> No need to release the plugin independantly - we should
do a full
> surefire release. The branch for 2.3.1 already exists.
>
> We just have 4 issues to resolve before it shold be
released: http://
> jira.codehaus.org/secure/IssueNavigator.jspa?
>
reset=true&mode=hide&sorter/order=DESC&sorter/
>
field=priority&resolution=-1&pid=10541&fixfor=13
251
>
> One of them, 297, was the one that needed windows
testing. Dennis and
> I looked at it at ApacheCon. I think, if you see my
comment, that
> basically the behaviour is now consistent across
versions and we just
> need to document that only certain styles of quoting of
arguments
> work. You probably understand the problem there
already. The key
> thing is that testing needs to occur both across
surefire versions
> (2.2, 2.3 which supposedly regressed, and
2.3.1-SNAPSHOT) and maven
> versions (2.0.5 and 2.0.6, since 2.0.6 changed the
behaviour of
> plexus-utils in plugins).
>
> Does that make sense?

There are two I have commented on that looks like
PLXUTILS-31 regression issues.

The others I can not comment on.