Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: infrastructure@apache.org
Subject: Re: Unable to add public key to
 https://svn.apache.org/repos/asf/maven/project/KEYS
Date: Thu, 30 Jul 2009 08:55:46 -0400
User-Agent: KMail/1.11.4 (Linux/2.6.30-gentoo-r1; KDE/4.2.4; x86_64; ; )
Cc: "Snitkovsky, Martin" <martin.snitkovsky@hp.com>,
 "repository@apache.org" <repository@apache.org>,
 "wink-dev@incubator.apache.org" <wink-dev@incubator.apache.org>
References: 
 <2C60AA1B234AC84D8486DC6BA56275FC4980E140E4@GVW1163EXB.americas.hpqcorp.net>
In-Reply-To: 
 <2C60AA1B234AC84D8486DC6BA56275FC4980E140E4@GVW1163EXB.americas.hpqcorp.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907300855.46495.dkulp@apache.org>

On Thu July 30 2009 8:48:07 am Snitkovsky, Martin wrote:
> Hi,
>
> We are planning to release Wink project with Maven.
>
> Based on http://maven.apache.org/developers/release/releasing.html, release
> manager should add his public key to
> https://svn.apache.org/repos/asf/maven/project/KEYS

Uh...  no.   That KEYS file is for the Maven project.   Only Maven release 
managers should be adding keys there.

You need to create one in your own project someplace.   (usually 
wink/trunk/KEYS so it gets tagged with releases, but some just put it in 
wink/KEYS)

It would need to be copied to the dist directory as part of the release as 
well.

Dan


>
> I was trying to do it, but failed with:
>
>
>
> svn: Commit failed (details follow):
>
> svn: CHECKOUT of '/repos/asf/!svn/ver/782204/maven/project/KEYS': 403
> Forbidden
>
>
>
> Do I need special permissions to be granted?
>
>
>
> martin

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