Return-Path: X-Original-To: apmail-ant-dev-archive@www.apache.org Delivered-To: apmail-ant-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 535111067F for ; Fri, 26 Dec 2014 14:12:42 +0000 (UTC) Received: (qmail 25978 invoked by uid 500); 26 Dec 2014 14:12:42 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 25903 invoked by uid 500); 26 Dec 2014 14:12:42 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 25892 invoked by uid 99); 26 Dec 2014 14:12:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Dec 2014 14:12:40 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of nicolas.lalevee@hibnet.org does not designate 216.86.168.182 as permitted sender) Received: from [216.86.168.182] (HELO mxout-07.mxes.net) (216.86.168.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Dec 2014 14:12:14 +0000 Received: from [192.168.0.106] (unknown [82.253.25.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B1C1122E25F for ; Fri, 26 Dec 2014 09:12:10 -0500 (EST) From: =?utf-8?Q?Nicolas_Lalev=C3=A9e?= Content-Type: multipart/alternative; boundary="Apple-Mail=_9204EC3F-496D-4398-A4DE-8358E27568C6" Message-Id: <08E1F20B-0B54-48AE-BDD9-6C90003E70FB@hibnet.org> Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: [RESULT][VOTE] Ivy 2.4.0 Release - take 2 Date: Fri, 26 Dec 2014 15:12:09 +0100 References: <5B8B9EF9-B9FD-4148-8702-64EA3C0C745A@hibnet.org> <871to2h5p7.fsf@v35516.1blu.de> <290A6BF5-0A1E-49EA-952E-AA0ACA5D71B0@gmx.de> <2720261C-ED14-488A-9D7C-D6A8B5596AD3@hibnet.org> To: Ant Developers List In-Reply-To: <2720261C-ED14-488A-9D7C-D6A8B5596AD3@hibnet.org> X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_9204EC3F-496D-4398-A4DE-8358E27568C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Counting my own +1, we have three +1 and one -1. The vote pass. I will = publish the release. Nicolas > Le 22 d=E9c. 2014 =E0 17:57, Nicolas Lalev=E9e = a =E9crit : >=20 > I have signed the tag: > See = https://git-wip-us.apache.org/repos/asf?p=3Dant-ivy.git;a=3Dtag;h=3Drefs/t= ags/2.4.0 = = > >=20 > I=92ve also build the updatesite ready to be published: > = https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivy-2.4.0.fina= l_20141213170938/ = = > >=20 > And I=92ve pushed the jars to the Nexus staging repository: > https://repository.apache.org/content/repositories/orgapacheant-1006/ = >=20 > So I think we=92re good. For now we have one -1 and three +1 = (including me). >=20 > I=92ll keep the vote open a couple of days, to be sure everyone had = the time to vote. And I=92ll promote the artifacts. >=20 > Nicolas >=20 >> Le 17 d=E9c. 2014 =E0 14:25, Nicolas Lalev=E9e = > a =E9crit= : >>=20 >>=20 >>> Le 17 d=E9c. 2014 =E0 04:09, Antoine Levy Lambert a = =E9crit : >>>=20 >>> Nicolas, Jean-Louis, what are your thoughts ? >>>=20 >>> The problem reported by Stefan with the ivy.xml in the source = archive must be caused by something in the build process replacing the = ivy.xml of the source tree with an expanded version of the same file = generated when the task runs ? >>=20 >> The purpose of this change is that it fixes the dependencies of Ivy. = I see no particular harm here. >>=20 >> But as Stefan, generally speaking, I prefer the source release to be = an extract of the source repository. So there is no possible confusion. >>=20 >>> I guess a minor edit in the build file to make this modified version = of ivy.xml go somewhere under the build folder should address this issue = for this release and the next ones. >>>=20 >>> I have not spent myself a lot of time on ivy yet but I would like to = spend some in 2015 - or maybe even next week if my kids are busy out of = the house =85 >>>=20 >>> I also know how it feels when one creates a release candidate and = some minor problems are found and one has to again go through 20 steps = in a ReleaseInstructions document =85 >>=20 >> Actually releasing Ivy is quite straight forward, no issues with = that. >> See: http://ant.apache.org/ivy/history/trunk/dev/makerelease.html = = > >> Probably the signing of the artifacts can be more automatic. I have = seen there is ant target for that but I haven=92t tested it yet. >>=20 >> What trouble me more is what is the exact process to push artifacts = into Maven repo after the release. And we=92ll need to figure out how to = push it into the Eclipse updatesite too. >>=20 >>> But I am sure we will get there finally. >>=20 >> I am sure too. We have to either be patient or actively act on it, = depending on our available time. >>=20 >>> On Dec 14, 2014, at 5:43 AM, Stefan Bodewig = wrote: >>>=20 >>>> We should be using signed tags (git tag -s or -u) rather than >>>> lightweight tags for releases. I know we haven't cut any releases = from >>>> git so far, so we'll be learning as we go along. >>=20 >> I do not know how it works, but I=92ll figure it out. And update the = release documentation. >>=20 >> Nicolas --Apple-Mail=_9204EC3F-496D-4398-A4DE-8358E27568C6--