archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: About Releasing 2.2.2
Date Mon, 20 Mar 2017 01:27:22 GMT
Hi Martin
There is some documentation on release here
http://archiva.apache.org/developers/releasing.html
the stage:copy last step is not up2date anymore.
I will update that this week.
Release is usually a manual process. I think you have to release redback
first?

I changed Jira setup and you should be able to create versions.
Let me know if you still cannot.

Cheers
Olivier


On 19 March 2017 at 04:15, Martin Stockhammer <m.stockhammer@web.de> wrote:

> Hi Olivier,
>
> and another question regarding this:
> To reorganize the JIRA issues, could you please add a 3.0 version to the
> JIRA
> project.
> And I think it makes sense to add a 3.1 version to move the unresolved
> issues,
> that are tagged with the 2.3 version.
>
>
> Greetings
>
> Martin
>
> Am Samstag, 18. März 2017, 17:49:32 CET schrieb Martin:
> > Hi,
> >
> > it would be good to release the 2.2.2 before merging the JPA branch.
> >
> > So some questions regarding this:
> > Olivier, I don't know if there are some special permissions needed, so
> are
> > you releasing it or may I do this (with your guidance)?
> >
> > I tried to understand the document about releasing but I'm not sure about
> > some points there.
> > 2.) Recreate the staging repository on archiva-repository.apache.org
> >    This is a manual process on the archiva-repository machine and not
> part
> > of the jenkins build?
> > 6.) Where do I have to check the webapp-tests?
> >
> > At least I can prepare the release notes document.
> >
> > Greetings
> >
> > Martin
>
>
>


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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message