Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com
 designates 64.233.184.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer;
        b=VYsLKxpQFnOdj3Pv2y22Fv74SRCHG+DupmEsP7IH+KC21hTuT3dkefjtyvwoa40ny6fNiej8qxWox6E2WGKrk0JZIIx024u8n/DKqq7TJEVB3hOeAUzONTQ8HqTpkFGd56yNqn7TF612rHUV7E4qzNVcXOmz60N+vs64+KPtUAg=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <937046e80708081208j46e9beb3mbc35d24c2667746d@mail.gmail.com>
References: <DED691DB-9C42-4962-9F65-3DD196A0DA82@planet57.com>
 <0678ED93-2490-489C-A0C9-3F3602ECCACA@iq80.com>
 <06F5CCF7-9E72-4CA4-A14E-A01A7B54ABD5@planet57.com>
 <9A8AF8BD-DE5C-484C-8956-F2AAE467A553@iq80.com>
 <17A5463B-EAD4-4939-87A4-F24873A153C9@hogstrom.org>
 <B1130DBE-E8A5-4A11-9DA8-95F971A1C8D4@planet57.com>
 <937046e80708081208j46e9beb3mbc35d24c2667746d@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--893521747
Message-Id: <8E260889-BECB-4FB8-B577-ECDC14F7E823@gmail.com>
From: Kevan Miller <kevan.miller@gmail.com>
Subject: Re: KEYS ?
Date: Fri, 12 Oct 2007 00:07:22 -0400
To: dev@geronimo.apache.org


--Apple-Mail-1--893521747
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Aug 8, 2007, at 3:08 PM, Jason Dillon wrote:

> And... this is done.  I don't know what else needs to be changed...  
> if anyone runs into any problems lemme know.
>
> The new location for this puppy in svn is:
>
>     https://svn.apache.org/repos/asf/geronimo/KEYS
>
> Props need to check the current trunk/* and branches/* (except for  
> release in progress branches) bits for other KEYS files and nuke them.

I just encountered our proliferation of KEYS files. From an Apache  
release signing perspective, I think the only important file is  
http://www.apache.org/dist/geronimo/KEYS. Probably makes sense to  
keep this file and https://svn.apache.org/repos/asf/geronimo/KEYS in  
sync (they are currently not in sync). I'm not sure if it's possible  
to automate this... Ideas?

I don't know of any reason to maintain KEYS files in any other svn  
directory. I propose we delete them from all non-tagged branches/ 
trunks in our svn tree. Thoughts?

--kevan


--Apple-Mail-1--893521747
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><BR><DIV><DIV>On Aug 8, 2007, at =
3:08 PM, Jason Dillon wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite">And... =
this is done. =A0I don't know what else needs to be changed... if anyone =
runs into any problems lemme know.<DIV><BR =
class=3D"webkit-block-placeholder"></DIV><DIV>The new location for this =
puppy in svn is:</DIV><DIV> <BR =
class=3D"webkit-block-placeholder"></DIV><DIV>=A0=A0 =A0<A =
href=3D"https://svn.apache.org/repos/asf/geronimo/KEYS">https://svn.apache=
.org/repos/asf/geronimo/KEYS</A><DIV><BR =
class=3D"webkit-block-placeholder"></DIV><DIV>Props need to check the =
current trunk/* and branches/* (except for release in progress branches) =
bits for other KEYS files and nuke =
them.<BR></DIV></DIV></BLOCKQUOTE><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>I just encountered our =
proliferation of KEYS files. =46rom an Apache release signing =
perspective, I think the only important file is=A0<A =
href=3D"http://www.apache.org/dist/geronimo/KEYS">http://www.apache.org/di=
st/geronimo/KEYS</A>. Probably makes sense to keep this file and=A0<A =
href=3D"https://svn.apache.org/repos/asf/geronimo/KEYS">https://svn.apache=
.org/repos/asf/geronimo/KEYS</A> in sync (they are currently not in =
sync). I'm not sure if it's possible to automate this... =
Ideas?</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>I =
don't know of any reason to maintain KEYS files in any other svn =
directory. I propose we delete them from all non-tagged branches/trunks =
in our svn tree. Thoughts?</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>--kevan</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><BR></DIV><BR></BODY></HTML>=

--Apple-Mail-1--893521747--