From easyant-dev-return-333-apmail-incubator-easyant-dev-archive=incubator.apache.org@incubator.apache.org Fri Dec 28 16:43:08 2012 Return-Path: X-Original-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4F8A8D465 for ; Fri, 28 Dec 2012 16:43:08 +0000 (UTC) Received: (qmail 56732 invoked by uid 500); 28 Dec 2012 16:43:08 -0000 Delivered-To: apmail-incubator-easyant-dev-archive@incubator.apache.org Received: (qmail 56697 invoked by uid 500); 28 Dec 2012 16:43:08 -0000 Mailing-List: contact easyant-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: easyant-dev@incubator.apache.org Delivered-To: mailing list easyant-dev@incubator.apache.org Received: (qmail 56689 invoked by uid 99); 28 Dec 2012 16:43:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 16:43:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jeanlouis.boudart@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qa0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 16:43:02 +0000 Received: by mail-qa0-f44.google.com with SMTP id z4so9595938qan.17 for ; Fri, 28 Dec 2012 08:42:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rtkY9QbUET32kVpJWnqkySQQ/BTDEuNJkfRjmle22xk=; b=CvyOjE9Xp78pJaLqk0ROFcOmg67oZKPghJM9BC6W29OLCfKczkCcDjekOHjcYL9D+d w9yuzvkfh08BV/GsL6FVUD0DA1R5GCZ5uLDiY4GwuetYZ3vkHdxKNHH8Q/eWHH3/Wyim 179PTtShYGSC3KulyHR6hhrrx6UQYOzMHickTBE1xVdcmIIrbL5Gf7aqtpVGBwryvrsU k2/7+6kSFumgz7ExmjNlT45ZukAgP3SzfUhVxJJh66M25p85gEHPDDqm5jXl3FvN0aSz GRDTnQLXHD8LfuYJjhe2fGOymEzVkchJByYsPSXv2dmtObmEB0jDYvDMW3QXqiFAsOaE kcxg== MIME-Version: 1.0 Received: by 10.49.59.131 with SMTP id z3mr18841199qeq.1.1356712961098; Fri, 28 Dec 2012 08:42:41 -0800 (PST) Received: by 10.49.81.195 with HTTP; Fri, 28 Dec 2012 08:42:40 -0800 (PST) In-Reply-To: References: Date: Fri, 28 Dec 2012 17:42:40 +0100 Message-ID: Subject: Re: A first release process From: Jean-Louis Boudart To: easyant-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=047d7b677bf41bc40504d1ec5add X-Virus-Checked: Checked by ClamAV on apache.org --047d7b677bf41bc40504d1ec5add Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sounds good for me. But i'm wondering if it won't be safer to replace the step : * invoke ant install-all: it will put every plugins into a shared repository locally on the build machine by * invoke ant install-all: it will put every plugins into a staging repository on repo.easyant.org For the first release i agree that it doesn't change anything. But for future, plugins could be released individually. To make them accessible (as they will not be in the main distribution) repo.easyant.orgcould be a good host. Like for the main distribution, we could use a staging area to make them accessible before being definitivly "public" (or "stable"). WDYT ? 2012/12/28 Nicolas Lalev=E9e > So we have EasyAnt core, the end user executable, and the EasyAnt plugins= , > buildtypes and skeletons (the build.xml pieces) to release. > > All core and plugins have a build based on EasyAnt. Since this build loop= , > I have setup some very basic build.xml so we can bootstrap a first releas= e. > > Here is the process I am suggesting: > - in plugins, buildtypes and skeletons: > -- do a svn tag. > -- invoke ant distributions: it will build a easyant-xxxx-0.9-src.zip > package to be publish in the release area > -- invoke ant install-all: it will put every plugins into a shared > repository locally on the build machine > - in core: > -- do a svn tag > -- invoke ant run -Dtarget=3Ddistribution: this is building easyant, and > then running easyant with the plugins just installed in the shared repo. = At > the end we should have a easyant-core-0.9-bin.zip and a > easyant-core-0.9-src.zip ready to be published in the release area > - push the *-src.zip and *-bin.zip into the staging release area > - md5, sha1 and sign the zip files > - vote for the release > > Once the process released finished, the source of this 0.9 will be then > available via 4 zip files. A zip distribution will be available to downlo= ad > for end user for immediate use. > And as an after release process, we would make the plugins, buildtypes an= d > skeletons available via our repository on repo.easyant.org. > > Does it sound good for everyone ? > > Nicolas > > --=20 Jean Louis Boudart Independent consultant Apache EasyAnt commiter http://incubator.apache.org/easyant/ --047d7b677bf41bc40504d1ec5add--