You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Misty Stanley-Jones <mi...@apache.org> on 2016/09/26 16:33:15 UTC

Need hand-holding for 1.1.7 release management

Is anyone around who can help me with some of the release management
steps? I think I have updated the KEYS file correctly, but now I am
stuck on what my ~/.m2/settings.xml should look like. I think I'm most
of the way there...

Re: Need hand-holding for 1.1.7 release management

Posted by Ted Yu <yu...@gmail.com>.
Was there any action which was required for the release but is not
documented already ?

Thanks

On Mon, Sep 26, 2016 at 1:33 PM, Misty Stanley-Jones <mi...@apache.org>
wrote:

> Thanks, I have followed those steps and now I am attempting to build the
> RC. Let's see how it goes.
>
> On Tue, Sep 27, 2016, at 05:20 AM, Sean Busbey wrote:
> > My ~/.m2/settings.xml file looks like the example from the "pushing
> > stuff to maven" guide[1]:
> >
> > <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
> >   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >   xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> >                       http://maven.apache.org/xsd/settings-1.0.0.xsd">
> >   <servers>
> >     <!-- To publish a website using Maven -->
> >     <!-- To stage a release of some part of Maven -->
> >     <server>
> >       <id>apache.releases.https</id>
> >       <username>busbey
> >       </username>
> >       <password><!--   redacted encrypted password   -->
> >       </password>
> >     </server>
> >   </servers>
> > </settings>
> >
> > I don't bother including a section for publishing SNAPSHOTs because I
> > don't publish SNAPSHOTs.
> >
> > Note that you'll need to follow the maven password encryption guide to
> > avoid storing your plaintext ASF creds[2] and you should use Maven
> > 3.2.1+ so that you don't need to put the password(s) on the command
> > invocation.
> >
> >
> > [1]: http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
> > [2]: http://maven.apache.org/guides/mini/guide-encryption.html
> >
> > On Mon, Sep 26, 2016 at 11:33 AM, Misty Stanley-Jones <mi...@apache.org>
> > wrote:
> > > Is anyone around who can help me with some of the release management
> > > steps? I think I have updated the KEYS file correctly, but now I am
> > > stuck on what my ~/.m2/settings.xml should look like. I think I'm most
> > > of the way there...
> >
> >
> >
> > --
> > busbey
>

Re: Need hand-holding for 1.1.7 release management

Posted by Misty Stanley-Jones <mi...@apache.org>.
Thanks, I have followed those steps and now I am attempting to build the
RC. Let's see how it goes.

On Tue, Sep 27, 2016, at 05:20 AM, Sean Busbey wrote:
> My ~/.m2/settings.xml file looks like the example from the "pushing
> stuff to maven" guide[1]:
> 
> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
>                       http://maven.apache.org/xsd/settings-1.0.0.xsd">
>   <servers>
>     <!-- To publish a website using Maven -->
>     <!-- To stage a release of some part of Maven -->
>     <server>
>       <id>apache.releases.https</id>
>       <username>busbey
>       </username>
>       <password><!--   redacted encrypted password   -->
>       </password>
>     </server>
>   </servers>
> </settings>
> 
> I don't bother including a section for publishing SNAPSHOTs because I
> don't publish SNAPSHOTs.
> 
> Note that you'll need to follow the maven password encryption guide to
> avoid storing your plaintext ASF creds[2] and you should use Maven
> 3.2.1+ so that you don't need to put the password(s) on the command
> invocation.
> 
> 
> [1]: http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
> [2]: http://maven.apache.org/guides/mini/guide-encryption.html
> 
> On Mon, Sep 26, 2016 at 11:33 AM, Misty Stanley-Jones <mi...@apache.org>
> wrote:
> > Is anyone around who can help me with some of the release management
> > steps? I think I have updated the KEYS file correctly, but now I am
> > stuck on what my ~/.m2/settings.xml should look like. I think I'm most
> > of the way there...
> 
> 
> 
> -- 
> busbey

Re: Need hand-holding for 1.1.7 release management

Posted by Sean Busbey <bu...@cloudera.com>.
My ~/.m2/settings.xml file looks like the example from the "pushing
stuff to maven" guide[1]:

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <servers>
    <!-- To publish a website using Maven -->
    <!-- To stage a release of some part of Maven -->
    <server>
      <id>apache.releases.https</id>
      <username>busbey
      </username>
      <password><!--   redacted encrypted password   -->
      </password>
    </server>
  </servers>
</settings>

I don't bother including a section for publishing SNAPSHOTs because I
don't publish SNAPSHOTs.

Note that you'll need to follow the maven password encryption guide to
avoid storing your plaintext ASF creds[2] and you should use Maven
3.2.1+ so that you don't need to put the password(s) on the command
invocation.


[1]: http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
[2]: http://maven.apache.org/guides/mini/guide-encryption.html

On Mon, Sep 26, 2016 at 11:33 AM, Misty Stanley-Jones <mi...@apache.org> wrote:
> Is anyone around who can help me with some of the release management
> steps? I think I have updated the KEYS file correctly, but now I am
> stuck on what my ~/.m2/settings.xml should look like. I think I'm most
> of the way there...



-- 
busbey