I think if you can't commit or move to dist/release, the last bit of the
release, (moving them over) won't work. I didn't have the issue you
mentioned with the KEYS file, but I think you mentioned to me out of band
the two files were different before you got started (
https://dist.apache.org/repos/dist/dev/nifi/KEYS vs
https://dist.apache.org/repos/dist/release/nifi/KEYS) . I'll investigate
that bit.

I could be wrong, but if your key is in https://dist.apache.org/repos/
dist/dev/nifi/KEYS, then you would be able to put together the release
candidate even with the svn permission problems you're having, as that move
to dist/release comes only after the vote is successful.

I also don't know what the permissions _should_ be for dist/release, I did
some cursory searching on the ASF docs to find something, but was not


On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora <jsk...@gmail.com> wrote:

> I hit a problem working on the 0.7.1 release, I can't get my keys committed
> to the dist/release repository.
> I committed them to the dist/dev repo (
> https://dist.apache.org/repos/dist/dev/nifi/KEYS) but I cannot move the
> file to the dist/release repo or commit directly to it, both return "403
> forbidden" errors.
> Based on the NiFi Release Guidelines
> <http://nifi.apache.org/release-guide.html> I believe my keys need to be
> added before performing Maven release steps, so I'm stuck until I get this
> sorted out.
> I don't know if I'm doing something wrong or if there's a permission
> problem somewhere.  Should I be able to commit to dist/release?
> Has anyone had any problems like this in the past?
> Thanks for any help.  (I will be away from my computer until Saturday
> night, but will pick this back up Sunday.)
> Regards,
> Joe S

Reply via email to