Return-Path: X-Original-To: apmail-xalan-dev-archive@www.apache.org Delivered-To: apmail-xalan-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 321EB11DF5 for ; Thu, 17 Jul 2014 13:37:10 +0000 (UTC) Received: (qmail 98834 invoked by uid 500); 17 Jul 2014 13:37:10 -0000 Delivered-To: apmail-xalan-dev-archive@xalan.apache.org Received: (qmail 98800 invoked by uid 500); 17 Jul 2014 13:37:10 -0000 Mailing-List: contact dev-help@xalan.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@xalan.apache.org Delivered-To: mailing list dev@xalan.apache.org Received: (qmail 98783 invoked by uid 99); 17 Jul 2014 13:37:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 13:37:09 +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 janstey@gmail.com designates 209.85.160.181 as permitted sender) Received: from [209.85.160.181] (HELO mail-yk0-f181.google.com) (209.85.160.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 13:37:05 +0000 Received: by mail-yk0-f181.google.com with SMTP id q200so1159882ykb.26 for ; Thu, 17 Jul 2014 06:36:45 -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=Y2BeqxHBFKdqYo8pXFNuUSt8xVXsMsr/pq+lzCcc1Wk=; b=Eze3jLN8Q7mcHDlBjEYxi2BRSolzF2fYuqnaEppEVw1jWA1ziyDEGYaxtpuThl3oIE HiyNNDsQ7/gvTAc+V6hX1W9p+Qc1MdxZexeZA+9nX1GYUjhkB5CgZJcqRi73aaaCD0hE QSxi4xyt+3TFg54u4286Bye0VtFrz0oIEZ/h2Gi+WScih7xBP93VaQPRz9R6oozldSEx QsM76RZFRabv/uKRoktbtrWQvEvJyoFkzMXjR7pTFhG519dZD1+OCEWADDsyX572I9kC Hdhv7kSXSDnpu+NtpkcS9jbUiSWh34Bxd/eKeONSnOs1avLnndPype0Nzeief6h5oQXv b0Sw== MIME-Version: 1.0 X-Received: by 10.236.35.198 with SMTP id u46mr61619804yha.54.1405604204965; Thu, 17 Jul 2014 06:36:44 -0700 (PDT) Received: by 10.170.155.87 with HTTP; Thu, 17 Jul 2014 06:36:44 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Jul 2014 11:06:44 -0230 Message-ID: Subject: Re: Release mechanics issue releasing 2.7.2 From: Jon Anstey To: dev@xalan.apache.org Content-Type: multipart/alternative; boundary=20cf3005e06c54f4ec04fe63bb36 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3005e06c54f4ec04fe63bb36 Content-Type: text/plain; charset=UTF-8 Wondering were ASF infra able to fix the staging issue? Need any additional help with this? Cheers, Jon On Wed, Jul 9, 2014 at 9:21 AM, Jon Anstey wrote: > Yeah, exactly. I can only see camel, activemq, karaf, etc. So its either > there is no staging profile at all for xalan yet or that you just need to > be assigned to the proper role in nexus. > > > On Tue, Jul 8, 2014 at 11:34 PM, Gary Gregory > wrote: > >> Hi Jon, >> >> I only see three staging profiles (commons, httpcomponents, logging). Is >> that because I can only see profiles for which I am granted some rights? >> >> Gary >> >> >> On Tue, Jul 8, 2014 at 8:45 AM, Jon Anstey wrote: >> >>> Hi Gary, >>> >>> Yes, very true. It will happen again for the next release :-) I can't >>> fully assist with the nexus fixes though as I don't have karma to see the >>> xalan stuff. When you log a ticket with INFRA ( >>> https://issues.apache.org/jira/browse/INFRA) make sure to tag with >>> component "Nexus" so the right guy sees it. >>> >>> Also, if you want to check the staging config yourself, there should be >>> a staging profile for xalan here: >>> https://repository.apache.org/index.html#stagingProfiles >>> >>> Cheers, >>> Jon >>> >>> >>> >>> On Mon, Jul 7, 2014 at 6:06 PM, Gary Gregory >>> wrote: >>> >>>> Now that I think about it, we should probably go through infra to >>>> resolve theinitial problem. >>>> >>>> Gary >>>> >>>> >>>> -------- Original message -------- >>>> From: Jon Anstey >>>> Date:07/07/2014 15:19 (GMT-05:00) >>>> To: dev@xalan.apache.org >>>> Subject: Re: Release mechanics issue releasing 2.7.2 >>>> >>>> Hi guys, >>>> >>>> Do you still intend to deploy Xalan 2.7.2 to Maven central? From what >>>> I've seen on the list there were some nexus staging problems? Apache infra >>>> should be able to help with this but if you are too busy I could volunteer >>>> to do the manual upload process if you'd like: >>>> >>>> >>>> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository >>>> >>>> Let me know what you think. >>>> >>>> Cheers, >>>> Jon >>>> >>>> >>>> >>>> On Wed, Jun 25, 2014 at 4:35 PM, janstey wrote: >>>> >>>>> Apache infra should be able to fix any issues with the nexus staging >>>>> rules >>>>> for you. You can log a ticket at >>>>> https://issues.apache.org/jira/browse/INFRA >>>>> >>>>> Would be really nice to get this release in a Maven repo :-) >>>>> >>>>> Cheers, >>>>> Jon >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://apache-xml-project.6118.n7.nabble.com/Release-mechanics-issue-releasing-2-7-2-tp40993p41189.html >>>>> Sent from the Xalan - Dev mailing list archive at Nabble.com. >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org >>>>> For additional commands, e-mail: dev-help@xalan.apache.org >>>>> >>>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Jon >>>> --------------- >>>> Red Hat, Inc. >>>> Email: janstey@redhat.com >>>> Web: http://redhat.com >>>> Twitter: jon_anstey >>>> Blog: http://janstey.blogspot.com >>>> Author of Camel in Action: http://manning.com/ibsen >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Jon >>> --------------- >>> Red Hat, Inc. >>> Email: janstey@redhat.com >>> Web: http://redhat.com >>> Twitter: jon_anstey >>> Blog: http://janstey.blogspot.com >>> Author of Camel in Action: http://manning.com/ibsen >>> >> >> >> >> -- >> E-Mail: garydgregory@gmail.com | ggregory@apache.org >> Java Persistence with Hibernate, Second Edition >> >> JUnit in Action, Second Edition >> Spring Batch in Action >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> > > > > -- > Cheers, > Jon > --------------- > Red Hat, Inc. > Email: janstey@redhat.com > Web: http://redhat.com > Twitter: jon_anstey > Blog: http://janstey.blogspot.com > Author of Camel in Action: http://manning.com/ibsen > -- Cheers, Jon --------------- Red Hat, Inc. Email: janstey@redhat.com Web: http://redhat.com Twitter: jon_anstey Blog: http://janstey.blogspot.com Author of Camel in Action: http://manning.com/ibsen --20cf3005e06c54f4ec04fe63bb36 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Wondering were ASF infra able to fix the staging= issue? Need any additional help with this?

Cheers,
J= on


O= n Wed, Jul 9, 2014 at 9:21 AM, Jon Anstey <janstey@gmail.com> wrote:
Yeah, exactly. I can only s= ee camel, activemq, karaf, etc. So its either there is no staging profile a= t all for xalan yet or that you just need to be assigned to the proper role= in nexus.


On Tue, Jul 8, 2014 at 11:34 PM, Gary Gr= egory <garydgregory@gmail.com> wrote:
Hi Jon,

I only see three staging pr= ofiles (commons, httpcomponents, logging). Is that because I can only see p= rofiles for which I am granted some rights?

Gary


On Tue, Jul 8, 2014 at 8:45 AM, Jon Anst= ey <janstey@gmail.com> wrote:
Hi Gary,

Yes, very true. It will ha= ppen again for the next release :-) I can't fully assist with the nexus= fixes though as I don't have karma to see the xalan stuff. When you lo= g a ticket with INFRA (https://issues.apache.org/jira/browse/INFRA) make= sure to tag with component "Nexus" so the right guy sees it.

Also, if you want to check the staging config yourself, there should be= a staging profile for xalan here: https://repository.apache.or= g/index.html#stagingProfiles

Cheers,
Jon

=

On Mon, Jul 7, 2014 at 6:06 PM, Gary Gre= gory <garydgregory@gmail.com> wrote:
Now that I think about it, =C2=A0we sho= uld probably go through infra to resolve theinitial problem.=C2=A0

Gary


-------- Original message ------= --
From: Jon Anstey
Date:07/07/2014 15:19 (G= MT-05:00)
Subject: Re: Release mechanics issue releasing 2.7.2

Hi guys,

Do you still intend to deplo= y Xalan 2.7.2 to Maven central? From what I've seen on the list there w= ere some nexus staging problems? Apache infra should be able to help with t= his but if you are too busy I could volunteer to do the manual upload proce= ss if you'd like:

https://docs.so= natype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+= Repository

Let me know what you think.

Cheers,
Jon



On Wed, J= un 25, 2014 at 4:35 PM, janstey <janstey@gmail.com> wrote:
Apache infra should be able to fix any issue= s with the nexus staging rules
for you. You can log a ticket at https://issues.apache.org/jira/browse/INFRA=

Would be really nice to get this release in a Maven repo :-)

Cheers,
Jon



--
View this message in context: http://apache-xml-project.6118.n7.nabble.com/Release-mechanic= s-issue-releasing-2-7-2-tp40993p41189.html
Sent from the Xalan - Dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org




--
Cheers,
Jo= n
---------------
Red Hat, Inc.
Email: janstey@redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen



--
=
Cheers,
Jon
---------------
Red Hat, Inc.
=
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen



= --



--
Cheers,
Jo= n
---------------
Red Hat, Inc.
Email: janstey@redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen



--
C= heers,
Jon
---------------
Red Hat, Inc.
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen
--20cf3005e06c54f4ec04fe63bb36--