How do committers recommend that patch contributors (like me) get their patches committed? At the moment I'm thinking of this one: https://issues.apache.org/jira/browse/SOLR-2535 This is a regression bug. I found the bug, I added a patch which fixes the bug and tested that it was fixed. The tests are actually new tests that tested code that wasn't tested before. I put the "fix version" in JIRA as 3.3 at the time I did this, because it was ready to go. Well 3.3 came and went, and the version got bumped to 3.4. There are no processes in place for committers to recognize completed patches. I think that's a problem. It's very discouraging, as the contributor. I think prior to a release and ideally at other occasions, issues assigned to the next release number should actually be examined. Granted there are ~250 of them on the Solr side: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SOLR+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+12316683+ORDER+BY+priority+DESC And some initial triage could separate the wheat from the chaff.
~ David Smiley --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
