Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-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 41D6A10B55 for ; Sun, 23 Jun 2013 08:43:26 +0000 (UTC) Received: (qmail 38470 invoked by uid 500); 23 Jun 2013 08:43:26 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 37218 invoked by uid 500); 23 Jun 2013 08:43:20 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 37129 invoked by uid 99); 23 Jun 2013 08:43:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Jun 2013 08:43:18 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.mueller@gmail.com designates 209.85.219.41 as permitted sender) Received: from [209.85.219.41] (HELO mail-oa0-f41.google.com) (209.85.219.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Jun 2013 08:43:14 +0000 Received: by mail-oa0-f41.google.com with SMTP id n10so11067385oag.0 for ; Sun, 23 Jun 2013 01:42:54 -0700 (PDT) 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=uynZHKrG4gG9PLupH9UHCqMoeIP2dU0b12r9m915jMc=; b=KtLptKEL6tAyGWxLTdx7uoICwVzfRagv9Q8J00UXx9sf55nHowk41XDnCyPNHyS0Gu rGBwSd7IyqyA41tkl7btBsrPE5KB2ExfZyMFTfnLkLQH61KL2h8XgaBoTSk6CDTgAjqM KgIPuZeP3Za28CYJ3z/U9wMG8hbFyF9GTDTBugG+t3j1ODwjLzL3bPIzDwez1BOH/0EC IJk78QicWnvR6RocDvfMpgzuccbf1P+4guQb2D+vrnrpL2lTKfEW5uWqsAq0fw6zlzuB 5/gZAVRn2FDWPAOwF4G5tmfcfuxtbG43BmcsTT1sr9ZDSbp/G5N22j2Bk21tb2S1nkpu TcQg== MIME-Version: 1.0 X-Received: by 10.182.55.72 with SMTP id q8mr6217420obp.96.1371976974072; Sun, 23 Jun 2013 01:42:54 -0700 (PDT) Received: by 10.182.110.100 with HTTP; Sun, 23 Jun 2013 01:42:53 -0700 (PDT) Received: by 10.182.110.100 with HTTP; Sun, 23 Jun 2013 01:42:53 -0700 (PDT) In-Reply-To: <51C5CB01.4090600@gmail.com> References: <5193806D.4070605@gmail.com> <51A24201.40408@gmail.com> <51C5CB01.4090600@gmail.com> Date: Sun, 23 Jun 2013 10:42:53 +0200 Message-ID: Subject: Re: [DISCUSS] - Apache Camel 2.10.5 release From: =?ISO-8859-1?Q?Christian_M=FCller?= To: dev@camel.apache.org Content-Type: multipart/alternative; boundary=089e01538afc2e00b704dfce48ff X-Virus-Checked: Checked by ClamAV on apache.org --089e01538afc2e00b704dfce48ff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Do you know whether it works? I only could found this issue [1] which isn't resolved yet. However, somebody suggested to use the option: -Dmaven.scm.gitexe.sign_tags [1] http://jira.codehaus.org/browse/SCM-486 Best, Christian ----------------- Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 Did you remove the camel-2.10.5 tag prior to re-running release:prepare? The previous tag was not signed. Can you look if it'd be possible to sign the tag as well? Cheers, Hadrian On 06/22/2013 10:48 AM, Christian M=FCller wrote: > Probably I was running into another/other issues of the > maven-release-plugin in combination with GIT: > http://jira.codehaus.org/**browse/MRELEASE-812 > > I'm back to version 2.4.1 and use the following setting: > > LANG=3D'en_US.UTF-8' > > Now the tag contains the right version. Will running the > mvn release:perform > in a few hours (I have to move now - with my machine...). > > Best, > Christian > ----------------- > > Software Integration Specialist > > Apache Camel committer: https://camel.apache.org/team > V.P. Apache Camel: https://www.apache.org/**foundation/ > Apache Member: https://www.apache.org/**foundation/members.html > > https://www.linkedin.com/pub/**christian-mueller/11/551/642 > > > On Sat, Jun 22, 2013 at 2:00 PM, Christian M=FCller < > christian.mueller@gmail.com> wrote: > > It looks like I run into this issue: >> http://jira.codehaus.org/**browse/MRELEASE-695 >> Will downgrade the maven-release-plugin to 2.2.1 (the version we used >> before). >> >> Keep you posted... >> >> Best, >> Christian >> >> >> ----------------- >> >> Software Integration Specialist >> >> Apache Camel committer: https://camel.apache.org/team >> V.P. Apache Camel: https://www.apache.org/**foundation/ >> Apache Member: https://www.apache.org/**foundation/members.html >> >> https://www.linkedin.com/pub/**christian-mueller/11/551/642 >> >> >> On Fri, Jun 21, 2013 at 7:57 PM, Christian M=FCller < >> christian.mueller@gmail.com> wrote: >> >> This first run didn't went well. The artifacts were not uploaded to Nex= us >>> and the tagged Camel 2.10.5 release had the version number >>> 2.10.5-SNAPSHOT... >>> >>> Next try later today... >>> >>> Best, >>> Christian >>> ----------------- >>> >>> Software Integration Specialist >>> >>> Apache Camel committer: https://camel.apache.org/team >>> V.P. Apache Camel: https://www.apache.org/**foundation/ >>> Apache Member: https://www.apache.org/**foundation/members.html >>> >>> https://www.linkedin.com/pub/**christian-mueller/11/551/642 >>> >>> >>> On Fri, Jun 21, 2013 at 12:02 AM, Christian M=FCller < >>> christian.mueller@gmail.com> wrote: >>> >>> The >>>> mvn release:prepare -DdryRun=3Dtrue >>>> went well yet. >>>> >>>> Running >>>> mvn release:prepare >>>> now... >>>> >>>> Best, >>>> Christian >>>> ----------------- >>>> >>>> Software Integration Specialist >>>> >>>> Apache Camel committer: https://camel.apache.org/team >>>> V.P. Apache Camel: https://www.apache.org/**foundation/ >>>> Apache Member: https://www.apache.org/**foundation/members.html >>>> >>>> https://www.linkedin.com/pub/**christian-mueller/11/551/642 >>>> >>>> >>>> On Wed, Jun 19, 2013 at 11:10 PM, Christian M=FCller < >>>> christian.mueller@gmail.com> wrote: >>>> >>>> I'm working on it... >>>>> >>>>> Best, >>>>> Christian >>>>> >>>>> ----------------- >>>>> >>>>> Software Integration Specialist >>>>> >>>>> Apache Camel committer: https://camel.apache.org/team >>>>> V.P. Apache Camel: https://www.apache.org/**foundation/ >>>>> Apache Member: https://www.apache.org/**foundation/members.html >>>>> >>>>> https://www.linkedin.com/pub/**christian-mueller/11/551/642 >>>>> >>>>> >>>>> On Mon, Jun 17, 2013 at 4:43 PM, Claus Ibsen >>>> >wrote: >>>>> >>>>> Hi >>>>>> >>>>>> It would be great to get the 2.10.5 release started as this will hel= p >>>>>> iron out any glitches we have after the git migration. >>>>>> >>>>>> There will always be X number of tickets that ppl want to be >>>>>> fixed/backported/implemented etc. We cannot do them all. So doing a >>>>>> release is better than not. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 14, 2013 at 5:45 PM, Christian M=FCller >>>>>> wrote: >>>>>> >>>>>>> The Camel 2.10.5 release is overdue. We released Camel 2.10.4 almos= t >>>>>>> >>>>>> 4 >>>>>> >>>>>>> month ago... >>>>>>> >>>>>>> The git mirror issue is resolved. >>>>>>> >>>>>>> CAMEL-6309 and CAMEL-6309 are still open. Do we consider these as >>>>>>> >>>>>> critical? >>>>>> >>>>>>> If yes, somebody familiar with the camel-ftp component (Claus?) >>>>>>> >>>>>> should have >>>>>> >>>>>>> a look and fix this soon. >>>>>>> >>>>>>> Do we wait for something else? >>>>>>> >>>>>>> If we are ready beginning of next week, I could try to cut our firs= t >>>>>>> release using GIT if Hadrian hasn't the time to do it. Otherwise I'= m >>>>>>> >>>>>> happy >>>>>> >>>>>>> to support him by testing the release candidate... >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Christian M=FCller >>>>>>> ----------------- >>>>>>> >>>>>>> Software Integration Specialist >>>>>>> >>>>>>> Apache Camel committer: https://camel.apache.org/team >>>>>>> V.P. Apache Camel: https://www.apache.org/**foundation/ >>>>>>> Apache Member: https://www.apache.org/**foundation/members.html >>>>>>> >>>>>>> https://www.linkedin.com/pub/**christian-mueller/11/551/642 >>>>>>> >>>>>>> >>>>>>> On Sun, May 26, 2013 at 7:10 PM, Hadrian Zbarcea >>>>>> > >>>>>>> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> We have some time, as I am still waiting for infra to resolve the >>>>>>>> >>>>>>> git >>>>>> >>>>>>> mirror issue and I need to switch the release builds to use git tag= s >>>>>>>> instead of svn. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Hadrian >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 05/25/2013 10:26 AM, Christian M=FCller wrote: >>>>>>>> >>>>>>>> The two issues mentioned by Bengt are still open, but I can give >>>>>>>>> >>>>>>>> it a >>>>>> >>>>>>> try... >>>>>>>>> >>>>>>>>> Christian >>>>>>>>> >>>>>>>>> Sent from a mobile device >>>>>>>>> Am 24.05.2013 13:52 schrieb "Claus Ibsen" = : >>>>>>>>> >>>>>>>>> Hi >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Any news on the possibility of a 2.10.5 release. >>>>>>>>>> >>>>>>>>>> The next release will actually be out 50th release. So that is a >>>>>>>>>> >>>>>>>>> good >>>>>> >>>>>>> milestone to reach :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, May 15, 2013 at 2:32 PM, Hadrian Zbarcea < >>>>>>>>>> >>>>>>>>> hzbarcea@gmail.com> >>>>>> >>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Yep, it's about time. I will take care of the necessary change= s >>>>>>>>>> >>>>>>>>> to be >>>>>> >>>>>>> build system and get ready for the release. What are the issues >>>>>>>>>>> >>>>>>>>>> that >>>>>> >>>>>>> >>>>>>>>>>> still >>>>>>>>>> >>>>>>>>>> need to be finished for 2.10.5? Let's start closing down. >>>>>>>>>>> >>>>>>>>>>> Hadrian >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 05/15/2013 03:10 AM, Claus Ibsen wrote: >>>>>>>>>>> >>>>>>>>>>> Hi >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Its been 2.5 months ago we released 2.10.4. >>>>>>>>>>>> >>>>>>>>>>>> I think we should start considering doing a 2.10.5 release. >>>>>>>>>>>> >>>>>>>>>>> Which is >>>>>> >>>>>>> also needed by the ServiceMix team for any new 4.5.x releases of >>>>>>>>>>>> theirs. >>>>>>>>>>>> >>>>>>>>>>>> And since we migrated to git, it would be a good idea to cut a >>>>>>>>>>>> >>>>>>>>>>> release >>>>>> >>>>>>> to ensure that we can still do releases, and that we iron out >>>>>>>>>>>> >>>>>>>>>>> any >>>>>> >>>>>>> issues we encounter after the svn -> git change. >>>>>>>>>>>> >>>>>>>>>>>> Any thoughts? >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Claus Ibsen >>>>>>>>>>>> ----------------- >>>>>>>>>>>> www.camelone.org: The open source integration conference. >>>>>>>>>>>> >>>>>>>>>>>> Red Hat, Inc. >>>>>>>>>>>> FuseSource is now part of Red Hat >>>>>>>>>>>> Email: cibsen@redhat.com >>>>>>>>>>>> Web: http://fusesource.com >>>>>>>>>>>> Twitter: davsclaus >>>>>>>>>>>> Blog: http://davsclaus.com >>>>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Claus Ibsen >>>>>>>>>> ----------------- >>>>>>>>>> www.camelone.org: The open source integration conference. >>>>>>>>>> >>>>>>>>>> Red Hat, Inc. >>>>>>>>>> FuseSource is now part of Red Hat >>>>>>>>>> Email: cibsen@redhat.com >>>>>>>>>> Web: http://fusesource.com >>>>>>>>>> Twitter: davsclaus >>>>>>>>>> Blog: http://davsclaus.com >>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> ----------------- >>>>>> www.camelone.org: The open source integration conference. >>>>>> >>>>>> Red Hat, Inc. >>>>>> FuseSource is now part of Red Hat >>>>>> Email: cibsen@redhat.com >>>>>> Web: http://fusesource.com >>>>>> Twitter: davsclaus >>>>>> Blog: http://davsclaus.com >>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> > --089e01538afc2e00b704dfce48ff--