Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: dev@cxf.apache.org
Subject: Re: [DISCUSS] Use Nexus for releases and/or snapshots?
Date: Wed, 1 Jul 2009 13:44:39 -0400
User-Agent: KMail/1.11.4 (Linux/2.6.30-gentoo-r1; KDE/4.2.4; x86_64; ; )
Cc: David Bosschaert <david.bosschaert@gmail.com>
References: <200902191338.50203.dkulp@apache.org>
 <200907011053.33859.dkulp@apache.org>
 <a1e060230907010928l51e09a21n866fd720d5e99e2b@mail.gmail.com>
In-Reply-To: <a1e060230907010928l51e09a21n866fd720d5e99e2b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907011344.40708.dkulp@apache.org>

On Wed July 1 2009 12:28:03 pm David Bosschaert wrote:
> What would the impact be?

There are a couple things:

1) The release managers would need to add some settings into their 
settings.xml to allow them to deploy to repository.apache.org.   Not a huge 
deal.    

2) The "mvn release:prepare; mvn release:perform" steps are normal, but after 
the release:perform deploys, you would need to login to repository.apache.org 
to close the staging area as well as get the URL to the staging area that you 
will need for the vote thread.

The main difference is AFTER the vote.   With the current process, you need to 
use the funky maven-stage-plugin to copy from the staging area to your local 
disk where it packages it up and uploads it and unpacks and such.  

With nexus, you just login to repository.apache.org and click a few buttons to 
"Promote" the release.   It's very quick and easy.    If the vote doesn't 
pass, you login and have nexus delete the staging area.   

You can see the Maven PMC release process at:
http://maven.apache.org/developers/release/releasing.html
They have screen shots and such.

The main thing it saves is not requiring the SCP stuff to copy to/from 
people.apache.org (thus, a bit easier for windows folks), and not using the 
stage plugin saves a bunch of transferring large things back and forth.   For 
the main CXF stuff, that's about 100MB each way.

Dan


> Simply the fact that the releases are also hosted at
> repository.apache.org? That would be fine with me as long as they
> don't just disappear which seems to have happened to our deployed
> snapshots at the moment...
>
> David
>
> 2009/7/1 Daniel Kulp <dkulp@apache.org>:
> > Actually, this would apply to David and Glen and the other DOSGi folks as
> > well.  Thus, their input would be good.
> >
> > Dan
> >
> > On Wed July 1 2009 10:47:38 am Daniel Kulp wrote:
> >> OK.   With Maven 2.2.0 finally out, we should have a version of Maven
> >> that works with GPG plugin (and thus is usable for Apache releases) as
> >> well as provides functionality for encrypted passwords and such in
> >> settings.xml. Thus, I'd like to revisit this.
> >>
> >> Since our snapshots are already there, this really will just impact the
> >> release process, which mostly means it impacts me.   Obviously the
> >> instructions on the wiki for doing releases and such will need to be
> >> updated as well.
> >>
> >> Anyway, are there any objections?
> >>
> >> Dan
> >>
> >> On Thu February 19 2009 1:38:49 pm Daniel Kulp wrote:
> >> > Some of you may be aware that the Maven team (actually Sonatype) has
> >> > installed Nexus repository manager onto a zone at
> >> > http://repository.apache.org.    Thus, projects are now being given
> >> > the option to use the Nexus repository instead of the stuff on
> >> > people.apache.org for things like snapshots and/or releases.
> >> >
> >> > One main advantage is that it uses HTTPs for deploys.   No futzing
> >> > with ssh/scp to get deploys working.   You need to put a setting or
> >> > two in your settings.xml file for auth info, but that's it.  The
> >> > deploys will just work.
> >> >
> >> > From a release perspective, it also supports easy staging and
> >> > promotion. When a release is deployed, it goes into a staging area
> >> > automatically. We then call the vote and if the vote passes, it's a
> >> > push button promotion to deploy it to central.   Nexus handles all the
> >> > metadata and such.   You don't need the maven-stage-plugin anymore.
> >> >
> >> >
> >> > Now for the downsides:
> >> > 1) The https self signed cert they currently use requires some work to
> >> > embed it into your jre keystore.   They've asked for a real cert, but
> >> > haven't gotten it yet.
> >> >
> >> > 2) Requires a little user management to put all of use into the "cxf"
> >> > group (if only Apache had ldap....), but Sonatype and the Maven PMC is
> >> > willing to manage that.
> >> >
> >> > 3) User impact:  if we decide that snapshots should go to nexus (we
> >> > could just do releases), users that use the snapshots would need to
> >> > change their URL's to grab from the new URL.     The links on our wiki
> >> > would need to change as well.
> >> >
> >> > 4) Obviously, our release procedures wiki page would need major
> >> > updating.
> >> >
> >> > 5) Learning curve: something new.   You can see the maven release
> >> > docs: http://maven.apache.org/developers/release/releasing.html
> >> > for a kind of walkthrough of how it would work. (with screen shots!)
> >> >
> >> >
> >> > Anyway, I'd like to hear others thoughts.    It MOSTLY applies to
> >> > myself and Willem as we're the only ones that have done releases.  
> >> > However, the snapshot stuff applies to Benson and a couple others as
> >> > well.
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog