From continuum-dev-return-5846-apmail-maven-continuum-dev-archive=maven.apache.org@maven.apache.org Tue Mar 13 08:49:17 2007 Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 79648 invoked from network); 13 Mar 2007 08:49:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Mar 2007 08:49:12 -0000 Received: (qmail 73427 invoked by uid 500); 13 Mar 2007 08:49:20 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 73397 invoked by uid 500); 13 Mar 2007 08:49:19 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 73382 invoked by uid 99); 13 Mar 2007 08:49:19 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Mar 2007 01:49:19 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [193.19.64.142] (HELO ow-mustang.objectware.no) (193.19.64.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Mar 2007 01:49:07 -0700 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by ow-mustang.objectware.no (8.12.11.20060308/8.12.11) with ESMTP id l2D8jcR8010722 for ; Tue, 13 Mar 2007 09:45:39 +0100 Message-ID: <45F6633B.2060509@apache.org> Date: Tue, 13 Mar 2007 09:39:23 +0100 From: =?UTF-8?B?VHJ5Z3ZlIExhdWdzdMO4bA==?= User-Agent: Thunderbird 2.0b2 (X11/20070123) MIME-Version: 1.0 To: continuum-dev@maven.apache.org Subject: Re: Preparing for continuum-1.1-alpha-1 References: <5757A095-15CD-4808-96E5-DF2F420E1B13@apache.org> <45EF0A13.3090206@venisse.net> <45F51859.1030708@apache.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Jesse McConnell wrote: >> > I think we shouldn't worry about making these actually releases cut >> > with the maven-release-plugin. I say we just make a build and get it >> > available for download. Also tag the continuum trunk accordingly. >> > Then we ought to try to release a new alpha every few weeks until we >> > have the alpha-# issues converging towards 0. >> >> Why not? Using the Maven plugin is generally easier than doing it by >> hand. Only issue that comes to mind are snapshots dependencies. > > having to resolve the snapshot dependencies are precisely the reason I > didn't want to mess with the maven release plugin for this. I would > have to release a new plexus-security and probably a couple of other > little higgly piggly bits. I think we can get by with the timestamped > SNAPSHOT dependencies for these things, means we can release alpha's > more frequently as well since we don't have to deal with > micro-releasing the dependencies each time. +1 for timestamped snapshots. Can we get these pushed to the releases repository so it's possible to build the alpha later? Or perhaps we don't care about the exact reproducibility of the alphas? People can build the dependent sources from subversion after all (yay open source). >> Seems like a good pick, but I have a couple of comments: >> >> CONTINUUM-253: why? can't it be done after the release? > > it can, it is just done partially in a couple of places and I thought > it might be nice to have that all collated together, but yes..it can > be pushed a bit I'm just trying to push, it's totally up to you as you're doing the work and I'm just bitching. >> CONTINUUM-827: sounds to me like this is something that can take a >> while, is it worth waiting for? Remember that the target for the next >> alpha should be within a month. > > fine by me :) > >> What is the time estimate on completing all of the issues? > > I want to see this pushed this week and then every couple of weeks > from here on out. Shibby. -- Trygve