You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2007/01/22 08:06:53 UTC

Fwd: Merge MSUREFIRE and SUREFIRE in JIRA?

FYI

Begin forwarded message:

> From: Brett Porter <br...@apache.org>
> Date: 22 January 2007 6:05:28 PM
> To: surefire-dev@maven.apache.org
> Subject: Re: Merge MSUREFIRE and SUREFIRE in JIRA?
> Reply-To: surefire-dev@maven.apache.org
> List-Id: <surefire-dev.maven.apache.org>
> Message-Id: <D2...@apache.org>
>
> Ok, I've done this (and MSUREFIREREP too). I've updated SCM, the  
> sites, and changed the permissions on the old jira projects so that  
> they can't have new issues created and pointed the descriptions at  
> SUREFIRE.
>
> I've added a "plugin" and "report plugin" component to the SUREFIRE  
> JIRA and also changed the versions. 1.5 -> 1.5 (2.1 plugin), 2.0 ->  
> 2.0 (2.2 plugin) and so on. I added 2.0 (Report Plugin) as a  
> separate version. All things will next be versioned 2.3.
>
> Still to go: clean up the roadmap and get a new release together.
>
> - Brett
>
> On 22/01/2007, at 3:47 AM, Jason van Zyl wrote:
>
>> +1
>>
>> On 20 Jan 07, at 4:51 PM 20 Jan 07, Brett Porter wrote:
>>
>>> Hi,
>>>
>>> Now that the SVN areas have converged and the versions lined up,  
>>> should we move all the MSUREFIRE issues that are still open (or  
>>> closed for the currently unreleased version) to SUREFIRE?
>>>
>>> - Brett
>>>