OK, I created https://svn.apache.org/repos/asf/lucene/java/dist and
have committed the KEYS file from the last release. I also updated
http://wiki.apache.org/jakarta-lucene/ReleaseTodo to reference the url.
On Feb 21, 2007, at 12:38 PM, Doug Cutting wrote:
Chris Hostetter wrote:
: since we have different sets of committers for different sub-
projects,
: it probably makes more sense to have per-subproject KEYS files.
That
: way folks can add their own keys without altering our current
permission
: scheme.
yeah, it would certianly be a "paradigm shift" ... i suggested it
only
because there already is a PMC level KEYS file (for no clear
reason that i
know of)
I'd vote for removing that top-level one, since it only confuses
things.
(a second reason is that there *may* be some people who would have
more
faith in a centralized KEYS file for all Lucene projects then for
sub-project specific - i have no idea how people who worry about
signed releases feel about that)
Browsing http://www.apache.org/dist/, there are a variety of
styles. Many projects have no top-level KEYS file. The common rule
seems to be that a KEYS file applies to its containing directory
and all subdirectories of that directory, although the automatic
verification code does not require that, considering all KEYS files.
http://people.apache.org/~henkp/checker/sig.html
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org
Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/
LuceneFAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]