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
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 complete
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
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 is
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 luceneby 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 2.0/4.0)
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 bode...@apache.org wrote:
On 2011-12-01, Simone Chiaretta wrote:
Currently there is a bit of confusion in the list of
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 nuget
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
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 geobmx...@hotmail.comwrote:
I was about to send an email to i...@outercurve.org,
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:
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 geobmx...@hotmail.comwrote:
We also discussed a contrib
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
- 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 or
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
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 simone.chiare...@gmail.com
wrote:
Ok, I'll starting working on them (the nuspecs files in build folder).
When I get access to the Lucene.Net
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
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 mhern...@wickedsoftware.net 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
23 matches
Mail list logo
