I manually added the Cassandra deployer group. As far as repository.a.o is concerned, you're a committer now ;-)
On Thu, Dec 30, 2010 at 5:42 PM, Stephen Connolly <steph...@apache.org> wrote: > Brian, > OK so I have Cassandra set up for deployment but I am getting 401's when I > try to deploy (as I am not a committer).... can we set things up so I can > stage... I don't need to promote unless the Cassandra PMC are happy letting > me promote. > Thanks, > -Stephen > Note: I have included dev@cassandra.apache.org to keep people in the loop > > On 13 December 2010 20:18, Brian Fox <bri...@infinity.nu> wrote: >> >> Cassandra isn't configured in the repo yet, so you should see this >> doc: http://www.apache.org/dev/publishing-maven-artifacts.html >> >> then if you're not a committer, we can override the privs so you can stage >> it. >> >> On Mon, Dec 13, 2010 at 1:12 AM, Stephen Connolly >> <stephen.alan.conno...@gmail.com> wrote: >> > Brian, >> > >> > What permissions do I need to stage in gId org.apache.cassandra? Do I >> > need >> > commit access to cassandra, or can I just get the cassandra pmc chair to >> > ok >> > me staging while I create a patch for their existing build... I'm not >> > looking to do the promotion (although if the existing devs don't want to >> > promote themselves, well maybe I'll have to go there, but I just want to >> > verify that the patch works first) >> > >> > - Stephen >> > >> > --- >> > Sent from my Android phone, so random spelling mistakes, random nonsense >> > words and other nonsense are a direct result of using swype to type on >> > the >> > screen > >
