Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-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 6A45410699 for ; Sun, 29 Dec 2013 14:31:57 +0000 (UTC) Received: (qmail 32691 invoked by uid 500); 29 Dec 2013 14:31:52 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 32658 invoked by uid 500); 29 Dec 2013 14:31:46 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 32650 invoked by uid 99); 29 Dec 2013 14:31:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Dec 2013 14:31:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.150.250.48] (HELO kalnich.nine.ch) (217.150.250.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Dec 2013 14:31:36 +0000 Received: from [192.168.1.121] (77-57-198-202.dclient.hispeed.ch [77.57.198.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kalnich.nine.ch (Postfix) with ESMTPSA id C6CC6B80054 for ; Sun, 29 Dec 2013 15:31:14 +0100 (CET) Message-ID: <1388327474.31252.3.camel@ubuntu> Subject: Re: New release tools / release manager for HttpClient 4.3.2? From: Oleg Kalnichevski To: HttpComponents Project Date: Sun, 29 Dec 2013 15:31:14 +0100 In-Reply-To: <8e0fc7a85alpgs8ikrvwljrq.1388327098118@email.android.com> References: <8e0fc7a85alpgs8ikrvwljrq.1388327098118@email.android.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Sun, 2013-12-29 at 09:24 -0500, Gary Gregory wrote: > Oleg, > > Do you see a release needing to happen asap? > > Gary > No, not really. If you cannot get around to it by mid Jan I'll take over and we will re-try with the next release. Oleg > -------- Original message -------- > From: Oleg Kalnichevski > Date:12/29/2013 07:57 (GMT-05:00) > To: HttpComponents Project > Subject: Re: New release tools / release manager for HttpClient 4.3.2? > > On Sun, 2013-12-29 at 13:05 +0100, Oleg Kalnichevski wrote: > > On Sat, 2013-12-28 at 18:27 -0500, Gary Gregory wrote: > > > I can give it a go. > > > > > > Gary > > > > > > > Gary, > > HTTPCLIENT-1443 has been sorted out. HttpClient trunk is all yours. > > Cheers > > Oleg > > > > Great! I updated the release notes for the coming release, which you are > > very welcome to improve and expand. > > > > There is one thing that we should probably clarify first. > > HTTPCLIENT-1443 [1] is still marked as unresolved. We should quickly > > check with Francois-Xavier if more work is needed and whether or not > > this can wait until 4.3.3. > > > > I'll be around to help with the release scripts and other release > > related stuff. > > > > Please update and improve the release process guide [2] as you go. > > > > Oleg > > > > [1] https://issues.apache.org/jira/browse/HTTPCLIENT-1443 > > [2] http://wiki.apache.org/HttpComponents/HttpComponentsReleaseProcess > > > > > > > -------- Original message -------- > > > From: Oleg Kalnichevski > > > Date:12/28/2013 06:56 (GMT-05:00) > > > To: dev@hc.apache.org > > > Subject: New release tools / release manager for HttpClient 4.3.2? > > > > > > Folks, > > > > > > I finally managed to put together a complete release process guide based > > > on release automation tools I have been working on for the past 6 months > > > [1]. > > > > > > The release tools should now simplify the most tedious and error-prone > > > manual operations involved in a release. > > > > > > I actually managed to run the entire HttpCore 4.3.1 release process > > > using the release tools only. > > > > > > Would anyone want to volunteer to be a release manager for HttpClient > > > 4.3.2 and help me polish the scripts and the process guide? > > > > > > One would still need a fully functional Maven setup including GPG > > > integration for artifact signing (as before), but otherwise the release > > > process should no longer require any special tools beyond an IDE and a > > > browser. Even a SVN client is not required. > > > > > > Oleg > > > > > > [1] http://wiki.apache.org/HttpComponents/HttpComponentsReleaseProcess > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org > > > For additional commands, e-mail: dev-help@hc.apache.org > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org > > For additional commands, e-mail: dev-help@hc.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org > For additional commands, e-mail: dev-help@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org