Okay, cool
On Mon, Feb 21, 2011 at 11:27 AM, Robert Jordan robe...@gmx.net wrote:
On 21.02.2011 05:55, Stefan Bodewig wrote:
On 2011-02-20, Robert Jordan wrote:
On 20.02.2011 07:49, Stefan Bodewig wrote:
If you talk about strong naming assemblies then I don't have any
experience how a
All,
The mailing lists have been updated to include a subject line prefix of
[Lucene.Net].
Please update any mail filters you may have that relate.
Thanks,
Troy
All,
It seems there's some confusion about the term 'signed release' from
my question. I'm specifically referring to Apache's rules about
signing releases using OpenPGP. This is the part I need help with.
Creating a Strong Named Assembly (SNA) using a Strong Name Key (SNK)
file is easy and is
[
https://issues.apache.org/jira/browse/LUCENENET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Troy Howard updated LUCENENET-172:
--
Due Date: 28/Mar/11
Fix Version/s: (was: Lucene.Net 3.x)
Update website to reflect current status and information
Key: LUCENENET-402
URL: https://issues.apache.org/jira/browse/LUCENENET-402
Project: Lucene.Net
Issue Type: Sub-task
Improve site layout and design
--
Key: LUCENENET-403
URL: https://issues.apache.org/jira/browse/LUCENENET-403
Project: Lucene.Net
Issue Type: Sub-task
Components: Project Infrastructure
Improve brand logo design
-
Key: LUCENENET-404
URL: https://issues.apache.org/jira/browse/LUCENENET-404
Project: Lucene.Net
Issue Type: Sub-task
Components: Project Infrastructure
Reporter: Troy
[
https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997538#comment-12997538
]
Digy commented on LUCENENET-399:
2.9.3
[
https://issues.apache.org/jira/browse/LUCENENET-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-405:
---
Attachment: NGram.patch
Port: contrib/Analysis.NGram
Port: contrib/Analysis.NGram
Key: LUCENENET-405
URL: https://issues.apache.org/jira/browse/LUCENENET-405
Project: Lucene.Net
Issue Type: New Feature
Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4
After we have two files,
one contaning public+private key(Lucene.Net.snk)
{sn -k Lucene.Net.snk}
and the other containing just public key(Lucene.Net.Public.snk)
{sn -p Lucene.Net.snk Lucene.Net.Public.snk}
we can share Lucene.Net.snk via private
DIGY - Extracting the public key out is generally only used for delay
signing. I don't think delay signing would help our situation, because
it means an end user still needs our private key to make a complete
signed build.
As a side note, I just realized that the multiple-signers scenario I
On 2011-02-21, Troy Howard wrote:
If we keep the key private, how do we then manage it? Is there a place
to store these kinds of resources, where only the committers have
access?
If this is the route you wanted to go it would be easy to set up an svn
area that only committers had read access
On 2011-02-21, Troy Howard wrote:
As a general question about process around accepting software
contributions, one thing I'm a little confused about: How does
accepting this contribution differ from a normal contribution?
Not much.
By that I mean, suppose a developer contributed a
Please avoid doing that, it would result in two assemblies, built against
the same version of lucene.net being unable to operate, since each uses a
different snk.
See log4net 1.0.9 and 1.0.10 fiasco for how much problems this can cause.
On Tue, Feb 22, 2011 at 7:09 AM, Stefan Bodewig
15 matches
Mail list logo
