Yes, you can create a new Jira if there isn't one already. I believe you can create a new pull request with the Jira number in the title, and that gets automatically appended to the Jira issue. Other option is to create a patch and upload it to the Jira manually.
On Sat, Feb 27, 2016 at 11:52 AM, Benoit Vanalderweireldt < benoi...@hybhub.com> wrote: > Thank you guys, > > I have choose to add a test cases class after reading the code coverage > report, I have pushed a first pull requests adding test cases for > org.apache.solr.util.hll.NumberUtil (GitHub PR < > https://github.com/apache/lucene-solr/pull/15>). > > What I should do next, should I create a new task on Jira ? > > Benoit > > > On Feb 26, 2016, at 1:31 AM, Erick Erickson <erickerick...@gmail.com> > wrote: > > > > There are also other ways to help than coding. Documentation, Java docs, > > writing test cases (look at the code coverage reports and pick something > > not already covered). Review or comment on patches, work on the new > Angular > > JS UI. > > > > Try installing Solr and note any ambiguous docs and suggest better ones, > > the sky is the limit. > > > > There's a chronic need for better JavaDocs. > > > > In short, pick something about Solr/Lucene that bugs you and see what you > > can do to improve it ;) > > > > Welcome! > > Erick > > On Feb 26, 2016 14:07, "Shawn Heisey" <apa...@elyograg.org> wrote: > > > >> On 2/25/2016 4:34 PM, Benoit Vanalderweireldt wrote: > >>> I have just joined this mailing list, I would love to contribute to > >> Apache SOLR (I am a certified Java developer OCA and OCP) > >>> > >>> Can someone guide me and assign me a first task on Jira (my username is > >> : b.vanalderweireldt) ? > >> > >> Thanks for stepping up and offering to help out! Jan has given you some > >> good starting points. I had mostly written this message before that > >> reply came through, so here's some more info: > >> > >> You'll want to join the dev list. Most of the communication for a > >> specific issue will happen in Jira, but the dev list offers a place for > >> larger and miscellaneous discussions. Warning: Because all Jira > >> activity is sent to the dev list, it is a high-traffic list. Having the > >> ability to use filters on your email to direct messages to different > >> folders is a life-saver. > >> > >> Your initial message would have been more at home on the dev list, but > >> we're not terribly formal about enforcing that kind of separation. > >> Initial discussion for many issues is welcome on this list, and often > >> preferred before going to Jira. > >> > >> Normally issues are assigned to the committer that agrees to take on the > >> change and commit it. > >> > >> Take a look at the many open issues on Solr. You'll probably want to > >> start with an issue that's recently filed, not one that was filed years > >> ago. After you become more comfortable with the codebase and the > >> process, you'll be in a better position to tackle older issues. > >> > >> > >> > https://issues.apache.org/jira/browse/SOLR/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel > >> > >> A highly filtered and likely more relevant list: > >> > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SOLR%20AND%20labels%20in%20%28beginners%2C%20newdev%29%20AND%20status%20not%20in%20%28resolved%2C%20closed%29 > >> > >> Thanks, > >> Shawn > >> > >> > >
