Hey All,
I'm happy to announce that we've released Lucene.Net 2.9.4. Check out the
download page (http://incubator.apache.org/lucene.net/download.html) to get
links to the source or binary files
~Prescott
[
https://issues.apache.org/jira/browse/LUCENENET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser closed LUCENENET-453.
-
> Many files need proper svn properties to set the linefeeds
> ---
[
https://issues.apache.org/jira/browse/LUCENENET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser resolved LUCENENET-453.
---
Resolution: Fixed
Fix Version/s: Lucene.Net 2.9.4
Assignee: Prescot
With 2.9.4 out the door, do we merge 3.0.3 into the trunk? How do we want to
handle this?
On 2011-12-01, Prescott Nasser wrote:
> The december board report has been updated:
> http://wiki.apache.org/incubator/December2011
Thanks!
> Please review and adjust as needed,
I've renamed your "Goals for graduation" section to "Long term goals" as
I don't see any reason why you'd need to co
>
> Therefore I've also added to the report that I plan to push you out of
> the Incubator soonish. 8-)
I'll not to let the door hit us on the way out
On 2011-12-01, Prescott Nasser wrote:
> I'm happy to announce that we've released Lucene.Net 2.9.4.
Congratulations all.
It may be a good idea to flesh this out a bit with details of what has
changed and sending an announcement to announce@apache as well (you must
use your @apache.org address in
Dears,
now, in the .NET ecosystem of opensource libraries it is super important to
have the nuget package released in sync with the binary release. Actually
many project are even just releasing the nuget package.
Currently there is a bit of confusion in the list of packages:
- There is "Lucene
Sorry, I'm behind - just reading the Nuget Documentation now.
I think we want to use "Lucene.Net", I agree with everything else, but I have
no idea how to modify the other packages. I'm also not sure how to sign our
our code base
> now, in the .NET ecosystem of opensource librar
We also discussed a contrib package - but we never really had a decision if we
should be doing one package per contrib project or a single contrib project.
> Date: Thu, 1 Dec 2011 10:00:24 +0100
> From: simone.chiare...@gmail.com
> To: lucene-net-dev@luc
I saw the current version is "strongly signed", that's why I added it.
Usually none releases signed versions, because users usually sign them with
their own key anyway, so if it was for me I'd skip that.
For the next release it would be great to add a step to the build script so
that the package i
On 2011-12-01, Simone Chiaretta wrote:
> Currently there is a bit of confusion in the list of packages:
>- There is "Lucene" with project id "lucene"by Apache SF relased on jan
>11 frozen on version 2.9.2.2 http://nuget.org/List/Packages/Lucene
>- There is "Lucene.Net - (strong named
So, no access to that packages via admin to delete them?
Shall I contact someone of the nuget team to sort that out?
Simone
On Thu, Dec 1, 2011 at 10:21 AM, Stefan Bodewig wrote:
> On 2011-12-01, Simone Chiaretta wrote:
>
> > Currently there is a bit of confusion in the list of packages:
>
> >
I was about to send an email to i...@outercurve.org, but if you have a better
connection that would be helpful, yes.
I just tried publishing under Lucene.Net and got shot down
> Date: Thu, 1 Dec 2011 10:23:19 +0100
> From: simone.chiare...@gmail.com
The other weird thing is that if I try to contact "the owner" of the
package it says "no owner for this package"
Simo
On Thu, Dec 1, 2011 at 10:23 AM, Simone Chiaretta <
simone.chiare...@gmail.com> wrote:
> So, no access to that packages via admin to delete them?
> Shall I contact someone of the
Sure, will contact Phil
On Thu, Dec 1, 2011 at 10:26 AM, Prescott Nasser wrote:
>
> I was about to send an email to i...@outercurve.org, but if you have a
> better connection that would be helpful, yes.
>
>
>
> I just tried publishing under Lucene.Net and got shot down
>
>
>
> ---
Thanks!
> Date: Thu, 1 Dec 2011 10:28:43 +0100
> From: simone.chiare...@gmail.com
> To: lucene-net-dev@lucene.apache.org
> Subject: Re: [Lucene.Net] Lucene.net nuget
>
> Sure, will contact Phil
>
> On Thu, Dec 1, 2011 at 10:26 AM, Prescott Nasser wrote:
>
Mail sent... let's see what he answers.
Simone
On Thu, Dec 1, 2011 at 10:28 AM, Simone Chiaretta <
simone.chiare...@gmail.com> wrote:
> Sure, will contact Phil
>
>
> On Thu, Dec 1, 2011 at 10:26 AM, Prescott Nasser wrote:
>
>>
>> I was about to send an email to i...@outercurve.org, but if you ha
Don't forget to tag the release in SubVersion.
The latest tag is RC3, and I assume that the trunk is the in-progress work on
version 3.0.3.
- Neal
-Original Message-
From: Prescott Nasser [mailto:geobmx...@hotmail.com]
Sent: Thursday, December 01, 2011 2:26 AM
To: lucene-net-...@incubato
if you look inside of trunk/build/scripts/ there are three nuspecs
under their respective folder names.
all, contrib, and core.
all is basically a dependency on contrib & core.
On Thu, Dec 1, 2011 at 4:06 AM, Prescott Nasser wrote:
>
> We also discussed a contrib package - but we never
Guys, if you want I can take ownership of the whole NuGet thing, from
getting hold of the right package id, to publishing the nuget pkgs, and
maybe adding a quickstart pkg
Let me know if it's ok, or someone is already working on that.
Simone
On Thu, Dec 1, 2011 at 3:58 PM, Michael Herndon wrote:
> - Lucene.Net to contain the core
> - Lucene.Contrib to contain the contrib and dep on Lucene.Net (there is
> no point in shipping contrib alone)
> - Lucene.Net.Sample to contain some samples (and a reference to
> Lucene.Net)
+1
> - Lucene: either empty with just a reference to Lucene.Net o
Ok, I'll starting working on them (the nuspecs files in build folder). When
I get access to the Lucene.Net pkg id I'll upload them.
If you give me your nuget gallery username I'll add you to the package
owners.
I'll also contact all other projects that are referencing to Lucene to tell
them to up
One last thing:
the binaries are just of .NET 4.0? or do we have different bins of 2.0 and
4.0?
Simone
On Thu, Dec 1, 2011 at 6:03 PM, Simone Chiaretta wrote:
> Ok, I'll starting working on them (the nuspecs files in build folder).
> When I get access to the Lucene.Net pkg id I'll upload them.
We have 4.0 only.
There is a way to slightly modify to compile to 2.0 ( digy replied to a thread
a day or two ago regarding this). However, that code didn't go through a vote,
and we believe there is a memory leak in it as well
Sent from my Windows Phone
From:
Userid: pnasser
Sent from my Windows Phone
From: Simone Chiaretta
Sent: 12/1/2011 9:03 AM
To: lucene-net-dev@lucene.apache.org
Subject: Re: [Lucene.Net] Lucene.net nuget
Ok, I'll starting working on them (the nuspecs files in build folder). When
I get access to th
there is actually registered for the lucene.net account for nuget.org. I'd
suggest we use that one since the committers have access the credentials
stored for the account.
If others are ok with Simone taking lead on this, I can forward those
credentials to him.
On Thu, Dec 1, 2011 at 12:04 PM,
Mine below
On Thu, Dec 1, 2011 at 7:28 PM, Michael Herndon wrote:
> On Thu, Dec 1, 2011 at 1:04 PM, Simone Chiaretta <
> simone.chiare...@gmail.com
> > wrote:
>
> > You mean a different impersonal Nuget account?
> >
>
> yes. the goal of the impersonal account was to allow committers to push
> nu
Added *pnasser* to all the nuget pkgs:
Lucene
Lucene.Contrib
Lucene.Net.All
Lucene.Net.Sample
Lucene.Net.Contrib
Any other nuget account I have to add as owner?
The dependency graph I'm doing is (shown inverted here)
- Lucene.net (strongly named assemby from apache site)
- Lucene (empty
Keep in mind tho that having the token checked in somewhere in the source
repository is not a good idea b/c someone could use it and publish malware
or trojans under your identity. So unless the token is stored outside the
source repository, it's not a good idea to have it in the CI.
- stored in
Good... no need to have another key...
Simo
---
Simone Chiaretta
@simonech
Sent from a tablet
On 01/dic/2011, at 21:04, Michael Herndon wrote:
> Keep in mind tho that having the token checked in somewhere in the source
> repository is not a good idea b/c someone could use it and publish malware
So, I created the packages using the binary release available on the
official site, but using the XML doc I got for building it on my machine.
Please test them and let me know if you find any problem:
http://dl.dropbox.com/u/5037284/Lucene.net-nuget/Lucene.2.9.4.1.zip
To test them unzip to file s
>
> Please test them and let me know if you find any problem:
> http://dl.dropbox.com/u/5037284/Lucene.net-nuget/Lucene.2.9.4.1.zip
>
Looks good
>
> I've seen ICSharpCode.SharpZipLib is always included in the bin folder
> after compiling, but if I'm not wrong it's only needed if compressed
33 matches
Mail list logo
