Wayne is typically my alter ego after the 10th cocktail. Did he show up? :)
I updated in another thread but the build server permissions are taken care of. On Thu, Apr 6, 2017 at 6:11 AM Shad Storhaug <[email protected]> wrote: > All I am saying is, it is YET ANOTHER account people have to sign up for. > It seems like a lot of friction could be removed here for people who want > to help out. It is difficult for people to contribute to Lucene.Net if they > have to sign up for and request permission for several different things. > For example, if someone were to submit a PR, they won't automatically be > emailed anything related from JIRA, the development mailing list, or the > user mailing list unless they specifically do the legwork to sign up for > those things. So the bugs related to the PR may go completely unnoticed by > the owner of the PR. I am signed up for JIRA, but have no permission to do > simple stuff like edit old issues to make them current or maintain the > version list. > > Microsoft has completely jumped ship from Microsoft-owned CodePlex (which > is now being shut down) to GitHub and is using GitHub features exclusively > (including the issue tracker). It seems like Apache should follow suit in > this regard. > > Itamar, do you have the ability to give me permission to edit the settings > in TeamCity so I can work on making the build script run tests in several > steps the way Wayne requested? > > Also, could you please give me ownership to the > https://www.nuget.org/packages/Spatial4n.Core.NTS/ feed, so I can upload > the beta of Spatial4n.Core.NTS there? > > Thanks, > Shad Storhaug (NightOwl888) > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Itamar Syn-Hershko > Sent: Thursday, April 6, 2017 4:42 PM > To: [email protected] > Subject: Re: JIRA Issue Tracker - Needs Updates > > Thanks Shad! unfortunately we have no access to github issues (standard > Apache process), JIRA and mailing list discussions should be enough even if > not the most comfortable. As far as I know anyone can sign in to JIRA to > comment and open issues, but I may be wrong. > > I will review all your recent excellent work very soon, it looks great and > hopefully we are finally nearing to a release! > > -- > > Itamar Syn-Hershko > Freelance Developer & Consultant > Elasticsearch Consulting Partner > Microsoft MVP | Lucene.NET PMC > http://code972.com | @synhershko <https://twitter.com/synhershko> > http://BigDataBoutique.co.il/ > > On Thu, Apr 6, 2017 at 11:36 AM, Shad Storhaug <[email protected]> > wrote: > > > Alternatively, enable issue tracking on GitHub. This would allow > > casual members of GitHub to participate in issue discussions, not just > > users who are brave enough (and can figure out how) to sign up for > > JIRA. And if there is nobody to maintain the JIRA monstrosity that > > requires special permission (and knowledge) to do, why not? > > > > -----Original Message----- > > From: Shad Storhaug [mailto:[email protected]] > > Sent: Thursday, April 6, 2017 1:26 PM > > To: [email protected] > > Subject: JIRA Issue Tracker - Needs Updates > > > > Hello, > > > > I am just getting started with the JIRA issue tracker. I noticed there > > are some problems because none of the latest Components or the latest > > Version are listed, and I don't seem to have access to add them. > > > > 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.Join > > > > 17. Lucene.Net.Memory > > > > 18. Lucene.Net.Misc > > > > 19. Lucene.Net.Queries > > > > 20. Lucene.Net.QueryParser > > > > 21. Lucene.Net.Replicator > > > > 22. Lucene.Net.Sandbox > > > > 23. Lucene.Net.Spatial > > > > 24. Lucene.Net.Suggest > > > > 25. Lucene.Net.TestFramework > > > > 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 would be happy to do it if someone would give me access. Or, if > > there are any suggestions on other ways to categorize issues belonging > > to these sub-projects without creating so many individual components, > > I am open to ideas. > > > > > > Thanks, > > Shad Storhaug (NightOwl888) > > >
