Just comment on https://issues.apache.org/jira/browse/INFRA-8428
On Fri, Oct 31, 2014 at 4:39 PM, Jordan Zimmerman < [email protected]> wrote: > Can you forward the email? They don’t seem to understand the problem (not > unusual). > > -JZ > > > On October 31, 2014 at 3:27:57 PM, Scott Blum ([email protected]) > wrote: > > Pinged them, they said they won't micro manage invididual wikis. They > gave me this link which is a "how to" on granting access: > > https://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions > > On Fri, Oct 31, 2014 at 12:46 PM, Jordan Zimmerman < > [email protected]> wrote: > >> Grrr - please ping INFRA again. For now, just give me the edits. >> >> >> On October 31, 2014 at 11:42:54 AM, Scott Blum ([email protected]) >> wrote: >> >> Ah good call. BTW: I still can't edit the wiki. :( I was going to add >> a little text to explain the binary vs. source releases. >> >> On Fri, Oct 31, 2014 at 12:40 PM, Jordan Zimmerman < >> [email protected]> wrote: >> >>> You can activate multiple profiles. That’s what I do. >>> >>> -JZ >>> >>> >>> On October 31, 2014 at 11:38:41 AM, Scott Blum ([email protected]) >>> wrote: >>> >>> Right, but when I activate that profile, that's when I want my apache >>> GPG key and curator-website-checkout-path to get set, right? I don't just >>> want that stuff active all the time when I'm doing non-Curator relative mvn >>> stuff. >>> >>> On Fri, Oct 31, 2014 at 12:37 PM, Jordan Zimmerman < >>> [email protected]> wrote: >>> >>>> BTW: I think the .m2 settings need another tiny update. The >>>> <profile> section needs: <id>apache-release</id> right? >>>> >>>> >>>> No - that profile is in the Apache parent pom. >>>> >>>> >>>> -JZ >>>> >>> >>> >> >
