Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of oching@exist.com designates
 64.233.166.178 as permitted sender)
Message-ID: <46CA573C.1090709@exist.com>
Date: Tue, 21 Aug 2007 11:08:44 +0800
From: Maria Odea Ching <oching@exist.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: archiva-dev@maven.apache.org
Subject: Re: Details for the upcoming 1.0-beta-2 release
References: <1a57a2980708200802wb1c091cyb256945685911a4c@mail.gmail.com>
 <C0B18067-8A35-464D-AAD2-C64DBFBEE354@apache.org>
 <46CA54A4.7040803@erdfelt.com>
In-Reply-To: <46CA54A4.7040803@erdfelt.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Joakim Erdfelt wrote:
> <-- Keen
> /
> (No, not Commander Keen)/
>

LOL

> I'm working as fast as I can (both velocity and quantity wise), I'll 
> have MRM-463 done this week.
>

Great! Thanks Joakim :)

> - Joakim
>
> Brett Porter wrote:
>> Looks great, thanks!
>>
>> Definitely worth a release with the stuff already in place, and I 
>> know Joakim is keen to have MRM-463 done. I'd like to get MRM-462 in, 
>> in case it causes any issues we need to address in a further beta 
>> since I touched a lot of stuff. I'm pretty sure I can close out 
>> what's assigned to me by Sat afternoon.
>>
>> - Brett
>>
>> On 21/08/2007, at 1:02 AM, Maria Odea Ching wrote:
>>
>>> Hi All,
>>>
>>> We're now preparing for the release of Archiva 1.0-beta-2. The 
>>> release is
>>> scheduled to take place over this coming weekend,
>>> and the details are specified below.
>>>
>>> 1. Issues that have already been Fixed/Closed:
>>>    - MRM-408 - The mvn deploy:deploy-file command gives "Parent doesn't
>>> exist" in a fresh install
>>>    - MRM-465 - [Load Testing] When asking for pages that require the
>>> effective-pom in high load, app becomes unresponsive
>>>    - MRM-467 - 500 error when user requested the dependency tree for
>>> artifact
>>>    - MRM-393 - Can't delete blacklist/whitelist pattern
>>>    - MRM-471 - Create a sample project that demonstrates how a 
>>> component can
>>> be plugged into Archiva
>>>    - MRM-374 - Changes aren't saved when updating Archiva Managed 
>>> Snapshot
>>> Repository
>>>    - MRM-407 - "Scanned" is always set to true even if unchecked in 
>>> the Edit
>>> Repository page
>>>    - MRM-436 - incorrect default cron expression for snapshots 
>>> repository
>>>    - MRM-383 - Unable to add new file types for Repository Scanning
>>>
>>>
>>> 2. Issues that will/may be included:
>>>
>>>    Assigned/In Progress:
>>>    - MRM-144 - fix miscellaneous tasks listed in important TODO items
>>>    - MRM-153 - when used as a maven1 proxy, Archiva should handle 
>>> relocation
>>> from maven2 poms
>>>    - MRM-243 - 507 Insufficient Storage when deploying artifact with 
>>> webdav
>>>    - MRM-398 - configure guest access by default for pre-configured
>>> repositories
>>>    - MRM-435 - need to review repository defaults
>>>    - MRM-437 - admin editing of proxy connectors fails in multiple 
>>> instances
>>>    - MRM-441 - removing a "remote repository" should not present the 
>>> page
>>> about handling content
>>>    - MRM-457 - don't display the snapshot removal options in the 
>>> repository
>>> list page if snapshots are not included
>>>    - MRM-462 - separate configuration of managed repositories from 
>>> remote
>>> repositories
>>>    - MRM-130 - improve search results page
>>>    - MRM-320 - ProxiedDavServer breaks update policy
>>>    - MRM-463 - Metadata merging doesn't work
>>>    - MRM-409 - No checking of invalid poms or artifacts during 
>>> repository
>>> scanning resulting to some objects not being found on the database
>>>    - MRM-453 - Create missing tests for repository purge
>>>    - MRM-449 - improvement to the reports form group search
>>>    - MRM-450 - change default label for repository ID report search 
>>> to "All
>>> repositories" instead of ""
>>>
>>>    Open:
>>>    - MRM-128 - better handling of jar artifacts without a pom
>>>    - MRM-196 - paginate results
>>>    - MRM-203 - Reports should be public, not an administration feature
>>>    - MRM-211 - Cannot use Archiva to get Maven1 Plugins
>>>    - MRM-308 - Maven1 requests are not served
>>>    - MRM-309 - relocated artifacts are not delivered
>>>    - MRM-354 - Show Artifact Reports results to HTTP ERROR: 500
>>>    - MRM-385 - Maven config docs refer to /proxy urls
>>>    - MRM-392 - pressing 'return' in the blacklist/whitelist form field
>>> submits whole form and validates, not pressing associated button
>>>    - MRM-428 - managed and remote repositories with same name causes
>>> problems   - MRM-432 -
>>>    - MRM-433 - Artifacts file types aren't take in account
>>>    - MRM-438 - broken images in the download box on the artifact page
>>>    - MRM-444 - Intermittent test failures on proxy
>>>    - MRM-458 - the NOTICE file is overzealous in declaring dependencies
>>>    - MRM-459 - prune the distributed dependencies
>>>    - MRM-472 - Re-enabled metadata tests in archiva-proxy
>>>    - MRM-473 - Fix the proxy code (and possibly the tests) to ensure 
>>> proper
>>> merging of metadata.xml files.
>>>    - MRM-474 - Create tests for non-snapshot metadata merging
>>>    - MRM-475 - Create tests for snapshot metadata merging
>>>
>>>
>>> Some of the Open issues above that will not make it for the release 
>>> this
>>> weekend will be moved to beta-3.
>>>
>>> Please feel free to comment :)
>>>
>>>
>>> Thanks,
>>> Deng
>>
>

-Deng