lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Powell ...@aaron-powell.com>
Subject RE: [Lucene.Net] Nuget, Lucene.Net, and Your Thoughts
Date Wed, 21 Sep 2011 04:11:22 GMT
I'm going to vote +1 for granular.

With the RC you could look at myget and have a Lucene.Net repository on there so people can
go for unstable on myget, stables on nuget.

Also, I came across this article which explains how to setup a build server to automatically
push to nuget/ myget which could be useful to the maintainers: http://brendanforster.com/doing-the-build-server-dance-with-nuget.html

Aaron Powell
MVP - Internet Explorer (Development) | FunnelWeb Team Member

http://apowell.me | http://twitter.com/slace | Skype: aaron.l.powell | Github | BitBucket


-----Original Message-----
From: Prescott Nasser [mailto:geobmx540@hotmail.com] 
Sent: Wednesday, 21 September 2011 2:05 PM
To: lucene-net-dev@lucene.apache.org
Subject: RE: [Lucene.Net] Nuget, Lucene.Net, and Your Thoughts


> Right now there are two packages: Lucene & Lucene.Contrib. My question 
> to the community is do you wish to finer grain packages, i.e. a 
> package for each contrib project or continue to keep it simple.
>


+1 Granular, we just need to be good about descriptions.


>
> Another topic to converse about is would you like to see an 
> out-of-band project nuget feed for nightly builds, branches with new 
> or experimental features, or stable code snapshots for a projected release?


Having a package for the latest RC would probably be a good idea 		 	   		  

Mime
View raw message