Staging a release

[Brent Atkinson <br...@gmail.com>]

Hi devs,

This weekend I was able to close out the last of the defects that were
scheduled for 1.5 moving them to 1.4.3. I left the remaining tasks and
feature work in 1.5.

I would like to stage a release candidate for a 1.4.3 release if there are
no objections, but I had some unresolved questions.

1.) According to http://continuum.apache.org/development/release.html:

The release will be staged in
> https://archiva-repository.apache.org/archiva/repository/continuum-releases/.
> You will need to set your user credentials for the Archiva repository in
> the <servers> section of yoursettings.xml file, under the
> archiva-repository.releases server ID.


I created an account on archiva-repository, but I believe I will need write
access to stage during release:perform. How do I get privileges or is it
unnecessary?

2.) I'm guessing that in during the release process, when the profile is
apache-release profile is activated, artifacts are signed using GPG. Do I
have to configure anything for this to work properly, such as configure
usage of particular keys?

3.) According to http://continuum.apache.org/development/release.html:

After the vote has passed, remove versions that no longer need to be
> downloaded from mirrors.


What is the criteria for removal? I tried searching for an answer to this,
but came up empty.

---

My understanding is that 3 is only important only after completing the
process, but I believe I will need to resolve 1 and 2 to stage a release. I
would love to update the relevant docs to clarify the points and start the
process as soon as possible.

I would be grateful for any help with this,

Brent

Re: Staging a release

[Olivier Lamy <ol...@apache.org>]

On 3 February 2015 at 07:53, Brent Atkinson <br...@gmail.com>
wrote:

> Hi devs,
>
> This weekend I was able to close out the last of the defects that were
> scheduled for 1.5 moving them to 1.4.3. I left the remaining tasks and
> feature work in 1.5.
>
> I would like to stage a release candidate for a 1.4.3 release if there are
> no objections, but I had some unresolved questions.
>
> 1.) According to http://continuum.apache.org/development/release.html:
>
> The release will be staged in
> >
> https://archiva-repository.apache.org/archiva/repository/continuum-releases/
> .
> > You will need to set your user credentials for the Archiva repository in
> > the <servers> section of yoursettings.xml file, under the
> > archiva-repository.releases server ID.
>
>
> I created an account on archiva-repository, but I believe I will need write
> access to stage during release:perform. How do I get privileges or is it
> unnecessary?
>

Done :-)


>
> 2.) I'm guessing that in during the release process, when the profile is
> apache-release profile is activated, artifacts are signed using GPG. Do I
> have to configure anything for this to work properly, such as configure
> usage of particular keys?
>

Yup must be here: https://dist.apache.org/repos/dist/release/continuum/KEYS

Note ATM there is no more sync between Archiva instance and maven central
via people.a.o

See https://issues.apache.org/jira/browse/INFRA-8762
I will ping regarding setup that...




>
> 3.) According to http://continuum.apache.org/development/release.html:
>
> After the vote has passed, remove versions that no longer need to be
> > downloaded from mirrors.
>
>
> What is the criteria for removal? I tried searching for an answer to this,
> but came up empty.
>
> ---
>
> My understanding is that 3 is only important only after completing the
> process, but I believe I will need to resolve 1 and 2 to stage a release. I
> would love to update the relevant docs to clarify the points and start the
> process as soon as possible.
>
> I would be grateful for any help with this,
>
> Brent
>



-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy