From easyant-dev-return-349-apmail-incubator-easyant-dev-archive=incubator.apache.org@incubator.apache.org Mon Jan 28 09:16:39 2013 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 46F1EEF63 for ; Mon, 28 Jan 2013 09:16:39 +0000 (UTC) Received: (qmail 36110 invoked by uid 500); 28 Jan 2013 09:16:39 -0000 Delivered-To: apmail-incubator-easyant-dev-archive@incubator.apache.org Received: (qmail 36058 invoked by uid 500); 28 Jan 2013 09:16:38 -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 35881 invoked by uid 99); 28 Jan 2013 09:16:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 09:16:30 +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 (athena.apache.org: domain of jeanlouis.boudart@gmail.com designates 209.85.216.46 as permitted sender) Received: from [209.85.216.46] (HELO mail-qa0-f46.google.com) (209.85.216.46) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 09:16:25 +0000 Received: by mail-qa0-f46.google.com with SMTP id o13so589782qaj.19 for ; Mon, 28 Jan 2013 01:16:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=oLvfZhwyWrVSqECntYzl78MUsqKhOLL/Uux+95UBE/k=; b=xJsKqG/ACVXjLiDtXam5+ycBXaDX9AIuIz36nc1xshLL8UeCPQwB0CY9hgCqIGVzG5 vg+tbpHLih37Zd74WgKKSbhdapo4pMaJRGtoJa5xPFWd6iirUNe8U7bIFOktFZR2ZolO fV2bw2ZE0Q0YvqbuDf25FP6Ow7SppdAh/w7CkvTNSaUOd5ffmM5BL3JeL/M/GN0dZIhD 6uuRxP/HX+w/yMrDBHblE0x9GY9Q2wlOVYH/4+P+Y1zN0Z1OZKFh92W5LKAzkUmO4Qai KqkqkJ+te2J5cz+sdz3kCEgfqRSrwrKyGfXRJiM+6otFxvQVsZjYG6zzeq84SUkuOUXC /HWg== MIME-Version: 1.0 X-Received: by 10.49.131.67 with SMTP id ok3mr17551778qeb.42.1359364565141; Mon, 28 Jan 2013 01:16:05 -0800 (PST) Received: by 10.49.81.195 with HTTP; Mon, 28 Jan 2013 01:16:05 -0800 (PST) In-Reply-To: <3760FC35-838D-4922-B0E9-6E6F8C59254E@hibnet.org> References: <5B69BD2D-CECD-471B-B5C3-3A26A3137592@hibnet.org> <63B785F5-D662-4BAC-A183-9AA36D600B82@hibnet.org> <8F9538DC-79BC-42BF-B6E5-BCF93C72A860@hibnet.org> <3760FC35-838D-4922-B0E9-6E6F8C59254E@hibnet.org> Date: Mon, 28 Jan 2013 10:16:05 +0100 Message-ID: Subject: Re: A first release process From: Jean-Louis Boudart To: easyant-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=047d7bdc06f00687d704d455ba55 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc06f00687d704d455ba55 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If this applies to core only, just updating the version attribute in core/trunk/module.ivy should do the trick without any other changes. Should we apply this version scheme also on buildtypes/skeletons etc... ? 2013/1/28 Nicolas Lalev=E9e > I had just a little trouble: the version should be 0.9-incubating. > What is the best way to make easyant core build to produce a distrib with > that version ? > If the solution is to just rename the artifact afterwards, I don't mind, > we can improve that later. > > Nicolas > > Le 25 janv. 2013 =E0 16:00, Nicolas Lalev=E9e a > =E9crit : > > > Le 24 janv. 2013 =E0 21:23, Jean-Louis Boudart < > jeanlouis.boudart@gmail.com> a =E9crit : > > > >> Ivy 2.3.0 release is almost ready, artifacts reached maven central rep= o. > >> Vote has ended without any veto. I assume official annouce is just a > >> question of time now. > >> > >> Could we start our release process now ? :p > > > > Definitively. > > I'll proceed soon, probably this week-end. > > > > Nicolas > > > >> Le 28 d=E9c. 2012 22:53, "Nicolas Lalev=E9e" a > >> =E9crit : > >> > >>> > >>> Le 28 d=E9c. 2012 =E0 22:51, Nicolas Lalev=E9e > a > >>> =E9crit : > >>> > >>>> > >>>> Le 28 d=E9c. 2012 =E0 22:05, Jean-Louis Boudart < > jeanlouis.boudart@gmail.com> > >>> a =E9crit : > >>>> > >>>>> I was thinking about it this morning when i saw Maarten's mail. > >>>>> Are we supposed to make a RC ? or directly a release? > >>>>> If apache process forces us to make a RC, then we could do the > release > >>> with > >>>>> current code base and then switch to 2.3.0-final. > >>>> > >>>> The ASF doesn't enforce anything about the quality of the code we ar= e > >>> releasing. It is "just" about IP, License, PMC vote (IMPC in our case= ), > >>> source distribution and probably also the svn tagging. So we do what = we > >>> want about versioning of releases. > >>>> > >>>>> In other case i would be in favor of waiting ivy 2.3.0 final releas= e. > >>>> > >>>> So we'll release an EasyAnt 0.9 with Ivy 2.3. > >>> > >>> Actually this will be a 0.9-incubating, as per the Incubator rules. > >>> > >>> Nicolas > >>> > >>>> > >>>> Nicolas > >>>> > >>>>> By the way, does it sound good if I try do a release just after the > >>> release > >>>>> of Ivy 2.3.0 (so we can use it in EasyAnt) ? Ivy release process > should > >>>>> start next week. > >>>>> > >>>>> Nicolas > >>>>> > >>>>> Le 28 d=E9c. 2012 =E0 20:14, Jean-Louis Boudart < > >>> jeanlouis.boudart@gmail.com> a > >>>>> =E9crit : > >>>>> > >>>>>> Oki, maybe it's a premature discussion. Let's go as you described > for > >>> the > >>>>>> first release and we will see in future how to enhance the process= . > >>>>>> > >>>>>> So no objection for me :) > >>>>>> Le 28 d=E9c. 2012 19:19, "Nicolas Lalev=E9e" < > nicolas.lalevee@hibnet.org> > >>> a > >>>>>> =E9crit : > >>>>>> > >>>>>>> > >>>>>>> Le 28 d=E9c. 2012 =E0 17:42, Jean-Louis Boudart < > >>> jeanlouis.boudart@gmail.com> > >>>>>>> a =E9crit : > >>>>>>> > >>>>>>>> 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 share= d > >>>>>>>> repository locally on the build machine > >>>>>>>> by > >>>>>>>> * invoke ant install-all: it will put every plugins into a stagi= ng > >>>>>>>> repository on repo.easyant.org > >>>>>>>> > >>>>>>>> For the first release i agree that it doesn't change anything. > >>>>>>> > >>>>>>> The problem with that change is that only people having write > access > >>> to > >>>>>>> repo.easyant.org could then build a distribution of easyant. We > must > >>> be > >>>>>>> sure there is a simple enough process for people to build easyant > from > >>>>> the > >>>>>>> sources. > >>>>>>> > >>>>>>>> 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 ? > >>>>>>> > >>>>>>> No objection. But we must make the difference between building a > >>>>>>> distribution and releasing. Building a distribution should be > >>> possible to > >>>>>>> anyone having the sources. Making a release should then be > building a > >>>>>>> distribution but pushed onto Apache infra for the sources at > least, or > >>>>>>> somewhere else as repo.easyant.org for the binaries. > >>>>>>> > >>>>>>> Nicolas > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> 2012/12/28 Nicolas Lalev=E9e > >>>>>>>> > >>>>>>>>> So we have EasyAnt core, the end user executable, and the EasyA= nt > >>>>>>> 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 > >>>>>>> release. > >>>>>>>>> > >>>>>>>>> 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 are= a > >>>>>>>>> - 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 > >>>>>>> download > >>>>>>>>> for end user for immediate use. > >>>>>>>>> And as an after release process, we would make the plugins, > >>> buildtypes > >>>>>>> and > >>>>>>>>> skeletons available via our repository on repo.easyant.org. > >>>>>>>>> > >>>>>>>>> Does it sound good for everyone ? > >>>>>>>>> > >>>>>>>>> Nicolas > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> Jean Louis Boudart > >>>>>>>> Independent consultant > >>>>>>>> Apache EasyAnt commiter http://incubator.apache.org/easyant/ > >>>>>>> > >>>>>>> > >>>> > >>> > >>> > > > > --=20 Jean Louis Boudart Independent consultant Apache EasyAnt commiter http://incubator.apache.org/easyant/ --047d7bdc06f00687d704d455ba55--