Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B5D17200C8C for ; Tue, 6 Jun 2017 13:53:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B4502160BC6; Tue, 6 Jun 2017 11:53:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0570E160BC3 for ; Tue, 6 Jun 2017 13:53:45 +0200 (CEST) Received: (qmail 64209 invoked by uid 500); 6 Jun 2017 11:53:45 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 64198 invoked by uid 99); 6 Jun 2017 11:53:45 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2017 11:53:45 +0000 Received: from [10.10.46.79] (unknown [87.191.39.154]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 906151A0029 for ; Tue, 6 Jun 2017 11:53:44 +0000 (UTC) From: Benedikt Ritter Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [all] Deploying components Date: Tue, 6 Jun 2017 13:53:40 +0200 References: <9D423223-DFEC-4BE2-BE43-BF810EA0ACE5@gmail.com> To: Commons Developers List In-Reply-To: Message-Id: <45E6F46F-E15F-41D5-A76C-9D22A4784895@apache.org> X-Mailer: Apple Mail (2.3273) archived-at: Tue, 06 Jun 2017 11:53:46 -0000 Hello Stian, > Am 05.06.2017 um 18:58 schrieb Stian Soiland-Reyes : >=20 > Personally I am happy about source distributions accompanying the jars = in > Maven Central, which are actually rebuildable as opposed to the > -source.jars. >=20 > they continue to be retrievable using Maven version mechanisms, = compares to > more fragile scripts crawling archive.apache.org (dist only contains = the > latest version). >=20 > The -bin archives are less useful, however I have used their hashes = during > RC testing to confirm the jars in staging reasonably match the RC in = dist > (this can also be achieved by simply unpacking the binary dist and > navigating to the jars) It=E2=80=99s a PITA to manually commit the archive to the distilled = area. This should be automated as part of the release process. Regards, Benedikt >=20 >=20 >=20 > On 28 May 2017 3:01 am, "Rob Tompkins" wrote: >=20 >> Hello all, >>=20 >> Benedikt and I were chatting last week about how the .tar and .zip >> distributions get uploaded to nexus during "mvn deploy=E2=80=9D and = how annoying >> that side effect of the deployment happens to be. Coincidentally, I = just >> ran across a note that Mladen Turk added at the end of the = commons-daemon >> release guide: >>=20 >> https://github.com/apache/commons-daemon/blob/trunk/ >> HOWTO-RELEASE.txt#L41-L43 > commons-daemon/blob/trunk/HOWTO-RELEASE.txt#L41-L43> >>=20 >> I=E2=80=99m thinking: (1) interesting note, knowing that the problem = still exists, >> and (2) I wonder if there would be community appetite for an attempt = at >> adding better automation to the release process. I=E2=80=99m betting = that with a >> little effort we probably could improve the release experience at = least a >> little. >>=20 >> Cheers, >> -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org