Stefan, Versions to Add
We also need version Lucene.Net 4.8.0 added to the Versions list. For the time being, I am going to add the issues to Lucene.Net 5.0 PCL (which we might be better off changing to 4.8.0 - note that it is not "portable", though). I was thinking that we should probably just consolidate Lucene.Net 5.0 PCL Lucene.Net 4.0 Lucene.Net 3.6 Into Lucene.Net 4.8.0 Components to Add 1. Lucene.Net.Analysis.Common 2. Lucene.Net.Analysis.ICU 3. Lucene.Net.Analysis.Kuromoji 4. Lucene.Net.Analysis.Morfologik 5. Lucene.Net.Analysis.Phonetic 6. Lucene.Net.Analysis.SmartCN 7. Lucene.Net.Analysis.Stempel 8. Lucene.Net.Analysis.UIMA 9. Lucene.Net.Benchmark 10. Lucene.Net.Classification 11. Lucene.Net.Codecs 12. Lucene.Net.Expressions 13. Lucene.Net.Facet 14. Lucene.Net.Grouping 15. Lucene.Net.Highlighter 16. Lucene.Net.ICU 17. Lucene.Net.Join 18. Lucene.Net.Memory 19. Lucene.Net.Misc 20. Lucene.Net.Queries 21. Lucene.Net.QueryParser 22. Lucene.Net.Replicator 23. Lucene.Net.Sandbox 24. Lucene.Net.Spatial 25. Lucene.Net.Suggest 26. Lucene.Net.TestFramework Thanks, Shad Storhaug (NightOwl888) -----Original Message----- From: Stefan Bodewig [mailto:[email protected]] Sent: Sunday, April 23, 2017 11:10 PM To: [email protected] Subject: Re: JIRA Issue Tracker - Needs Updates On 2017-04-23, Shad Storhaug wrote: > Stefan, >>> Just wondering if someone could either update JIRA or give me >>> permission to update it. >> I've granted you Committer access, let me know whether this is enough to >> make the changes you need to apply. > I am still not seeing any way to edit Versions or Components in the > control panel. While I'm trying to figure things out, maybe you can tell me what I should create. This may be faster :-) >>> We are ready to push the BETA to NuGet and we really should have the >>> issue tracker optimized to track bugs... >> This really sounds like something that could use a release vote ... > As for the vote, do note we have already had a discussion about this > (https://www.mail-archive.com/[email protected]/msg02830.html), > it has just taken awhile to come to fruition. I'm old (ask my children :-) and my memory is often failing me. What I was talking about is the good old Apache release vote[1] and I don't see the thread of last September touching on it. When we provide a release as Apache Lucene.NET - and it doesn't matter whether we call it an alpha, beta or final release - to the general public the PMC must vote an the actual release artifacts. Not just on the intent of creating them. > I think we should announce the new CI feed (below) and see if there > are any issues first before going to NuGet. Automated builds that go to the MyGet are fine as long as we label them developer snapshots and don't recommend them to the general public. We are relly walking a fine line here. Before you get me wrong, I really don't want t stop any momentum and am glad we are as close to a release as we are now. There are just a few rules that we need to adhere to, and all it is going to cost us is a formal vote that will run for about three days. Stefan [1] http://www.apache.org/legal/release-policy.html
