I think the process here is a bit different than in a real Apache project. We need to get approval from Incubator PMC on binaries that are exactly the same that we put into a real m2-repo. A podling can't simply put together a release. it needs an approval on some binaries and when that approval is there, the release process is ended.
Runing the release:perform after asking the incubator PMC would change this (IMO) -M On 2/13/07, Manfred Geiler <[EMAIL PROTECTED]> wrote:
No. "release:perform" ends the release process - after the vote! Just do a "mvn clean deploy -Psign-artifacts" (after you have checked that distributionManagement points to the correct staging dir) --Manfred On 2/13/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > so that means doing a "release:perform" to a staging repo (where ever that is) > to continue ? > > -M > > On 2/13/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote: > > We can do both, but I will focus on the binary.. > > > > Mvgr, > > Martin > > > > Matthias Wessendorf wrote: > > > Hi, > > > > > > I was able to "prepare" the relase, based on the given feedback. Maven > > > created already a TAG for that (see [1]). > > > > > > Should we vote on the tag (meaning source files) or on a binary artifact ? > > > I think here, in the Trinidad DEV list we should vote on the source files. > > > > > > After that, when moving to [EMAIL PROTECTED], we should as them for > > > approval, based on a binary release. > > > > > > Thanks for any kind of feedback. > > > > > > -Matthias > > > > > > [1] > > > http://svn.apache.org/repos/asf/incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/ > > > > > > > > -- > Matthias Wessendorf > http://tinyurl.com/fmywh > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
-- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
