Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-dev@maven.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-Id: <B7D1132F-210E-4EB6-9228-833B0F74A504@apache.org>
From: Brett Porter <brett@apache.org>
To: archiva-dev@maven.apache.org
In-Reply-To: <47B9D6DF.40406@erdfelt.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Jira merge versions.
Date: Tue, 19 Feb 2008 07:36:08 +1100
References: <47B9D6DF.40406@erdfelt.com>

I'm unsure. I'd definitely leave 0.9 out on it's own regardless.

I kind of like the idea of merging, but I also hate to irreversibly  
lose information :)

Does archiving the alpha/beta releases achieve what you need? What is  
the noise in the reports you are referring to?

Thanks,
Brett

On 19/02/2008, at 6:05 AM, Joakim Erdfelt wrote:

> I'd like to merge a few older released versions together in Jira (to  
> help in reducing the noise on some of the reports.)
>
> What I'd like to do ...
>
> Take versions:
> * 0.9
> * 1.0-alpha-1
> * 1.0-alpha-2
> * 1.0-beta-1
> * 1.0-beta-2
> * 1.0-beta-3
> * 1.0-beta-4
>
> And merge them into:
> * 1.0
>
> Any objections?
>
> - Joakim

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/