Ok, makes sense to have it. That probably means we did request it somehow (PMC?).
But then our group/search settings are not configured properly. How would we go about fixing it? Regards, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 5 June 2017 at 15:52, Mike Drob <[email protected]> wrote: > I think the issue security level has to be around in order to keep some > issues private. For example, > https://issues.apache.org/jira/browse/SOLR-10031 before the 5.5.4 release. > > Not sure if there's an alternative model that will still allow for > responsible disclosure of security issues. > > Mike > > On Mon, Jun 5, 2017 at 2:46 PM, Alexandre Rafalovitch <[email protected]> > wrote: >> >> Because: https://issues.apache.org/jira/browse/INFRA-13729 >> >> TLDR: some GSOC 2017 issues were not visible to non-logged-in users >> for multiple Apache projects. INFRA thinks we opted in to the "Issue >> Secruity" field that is causing it, and perhaps deliberately picked >> non-optimal defaults/configuration. >> >> Any insight would be appreciated to see whether it is worth chasing >> this further. >> >> Regards, >> Alex. >> ---- >> http://www.solr-start.com/ - Resources for Solr users, new and experienced >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
