Re: [VOTE] Release Log4j 2.11.0-rc1

2018-03-12 Thread Matt Sicker
+1 Site review: * Front page header: "h3 Integrating with Application Servers" * MongoDB component link is a 404 * JIRA report is a blank page * Surefire report on homepage is a 404 * Wiki link in the header should point to Confluence now Artifacts check out. Built and tested with: macOS 10.13

Re: Chainsaw configured in Jenkins and JIRA

2018-03-12 Thread Robert Middleton
Looks good to me. :) -Robert Middleton On Mon, Mar 12, 2018 at 10:49 AM, Matt Sicker wrote: > Alright, permissions should match that of LOG4J2. Let me know if you're > having any issues viewing it now. > > On 12 March 2018 at 09:11, Matt Sicker wrote: > >> This appears to be beyond the scope of

Re: Chainsaw configured in Jenkins and JIRA

2018-03-12 Thread Matt Sicker
Alright, permissions should match that of LOG4J2. Let me know if you're having any issues viewing it now. On 12 March 2018 at 09:11, Matt Sicker wrote: > This appears to be beyond the scope of my permissions again, so I filed a > ticket: https://issues.apache.org/jira/browse/INFRA-16172 > > On 1

Re: Chainsaw configured in Jenkins and JIRA

2018-03-12 Thread Matt Sicker
This appears to be beyond the scope of my permissions again, so I filed a ticket: https://issues.apache.org/jira/browse/INFRA-16172 On 12 March 2018 at 09:07, Matt Sicker wrote: > No, that's not intentional. Thanks for the feedback! I'll see what's > misconfigured this morning and will report ba

Re: Chainsaw configured in Jenkins and JIRA

2018-03-12 Thread Matt Sicker
No, that's not intentional. Thanks for the feedback! I'll see what's misconfigured this morning and will report back. On 11 March 2018 at 21:45, Robert Middleton wrote: > While it now shows up under the 'logging' category, I still can't see > the project at all unless I'm logged in. I'm assumin