Re: Problem preparing to execute 0.7.1 release

[Tony Kurc]

Joes - it looks like nifi-0.7.1 is in dist/dev/nifi/ , and I just completed
an update of KEYS in dist/release/nifi.

Tony

On Sun, Oct 16, 2016 at 6:02 PM, Joe Witt  wrote:

> If the items are on dev/dist the vote can happen.  Once approved a pmc
> member can move them from there.
>
> Thanks!
> Joe
>
> On Oct 16, 2016 5:58 PM, "Tony Kurc"  wrote:
>
> Joe,
> For 0.7.1, I'll take care of getting KEYS right in the release directory. I
> believe that I (or another PMC member) can also perform the move to
> release. It sounds like once I get the KEYS sorted, we're ready for a vote.
>
> As for the perms on the dist directories, it sounds like we may have some
> things to sort out before the next committer (and not PMC member) can do a
> release, and we may need to update the docs.
>
> Tony
>
> On Sun, Oct 16, 2016 at 5:53 PM, Joe Skora  wrote:
>
> > 1. I was able to perform the release as you expected and create the
> > staging repository.  :-D
> >
> > 2. I have not sent the release vote email because the template states
> > "KEYS file available here:https://dist.apache.org/
> > repos/dist/release/nifi/KEYS" but my keys are not included there yet.
> >
> > 3. I contacted the INFRA team via HipChat and they said that normally
> only
> > the PMC can commit to dist/*, but the PMC can extend the privilege to
> > committers.  Thus, I should not have been able to commit to dist/dev
> > either.  (I've attached a copy of the chat.)
> >
> > So it appears that unless permissions are specially granted, the release
> > manager role does require PMC membership.
> >
> > How do you want to proceed?
> >
> > On Fri, Oct 14, 2016 at 5:09 PM, Tony Kurc  wrote:
> >
> >> Also, it looks like the difference between the KEYS file on dev and
> >> release
> >> prior to you adding your key to dev is that it looks like Joe
> Percivall's
> >> key was sort of added twice to the release repo.
> >>
> >> dev KEYS before Joe Skora addition:
> >>  https://dist.apache.org/repos/dist/dev/nifi/KEYS?p=14135
> >>
> >> release KEYS now :
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14117
> >>
> >> release KEYS before Joe Percivall addition (major difference is adding
> two
> >> identical key blocks)
> >> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14116
> >>
> >> We should tidy that up when the next release is ready.
> >>
> >>
> >> On Fri, Oct 14, 2016 at 2:10 PM, Joe Witt  wrote:
> >>
> >> > I'm thinking the same thing Tony.  Joe you should be able to do the
> >> > full process and we just might need to help with the final push of the
> >> > official bits to the release directory.  In parallel please submit a
> >> > request to INFRA on permissions for that folder.  Perhaps there is
> >> > something else I need to activate though I'm not aware of anything.
> >> >
> >> > Thanks
> >> > Joe
> >> >
> >> > On Fri, Oct 14, 2016 at 2:06 PM, Tony Kurc  wrote:
> >> > > 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
> >> > > successful.
> >> > >
> >> > > Tony
> >> > >
> >> > > On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora 
> 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
> >> > >>  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
> Sat

Re: Problem preparing to execute 0.7.1 release

[Joe Witt]

If the items are on dev/dist the vote can happen.  Once approved a pmc
member can move them from there.

Thanks!
Joe

On Oct 16, 2016 5:58 PM, "Tony Kurc"  wrote:

Joe,
For 0.7.1, I'll take care of getting KEYS right in the release directory. I
believe that I (or another PMC member) can also perform the move to
release. It sounds like once I get the KEYS sorted, we're ready for a vote.

As for the perms on the dist directories, it sounds like we may have some
things to sort out before the next committer (and not PMC member) can do a
release, and we may need to update the docs.

Tony

On Sun, Oct 16, 2016 at 5:53 PM, Joe Skora  wrote:

> 1. I was able to perform the release as you expected and create the
> staging repository.  :-D
>
> 2. I have not sent the release vote email because the template states
> "KEYS file available here:https://dist.apache.org/
> repos/dist/release/nifi/KEYS" but my keys are not included there yet.
>
> 3. I contacted the INFRA team via HipChat and they said that normally only
> the PMC can commit to dist/*, but the PMC can extend the privilege to
> committers.  Thus, I should not have been able to commit to dist/dev
> either.  (I've attached a copy of the chat.)
>
> So it appears that unless permissions are specially granted, the release
> manager role does require PMC membership.
>
> How do you want to proceed?
>
> On Fri, Oct 14, 2016 at 5:09 PM, Tony Kurc  wrote:
>
>> Also, it looks like the difference between the KEYS file on dev and
>> release
>> prior to you adding your key to dev is that it looks like Joe Percivall's
>> key was sort of added twice to the release repo.
>>
>> dev KEYS before Joe Skora addition:
>>  https://dist.apache.org/repos/dist/dev/nifi/KEYS?p=14135
>>
>> release KEYS now :
>> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14117
>>
>> release KEYS before Joe Percivall addition (major difference is adding
two
>> identical key blocks)
>> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14116
>>
>> We should tidy that up when the next release is ready.
>>
>>
>> On Fri, Oct 14, 2016 at 2:10 PM, Joe Witt  wrote:
>>
>> > I'm thinking the same thing Tony.  Joe you should be able to do the
>> > full process and we just might need to help with the final push of the
>> > official bits to the release directory.  In parallel please submit a
>> > request to INFRA on permissions for that folder.  Perhaps there is
>> > something else I need to activate though I'm not aware of anything.
>> >
>> > Thanks
>> > Joe
>> >
>> > On Fri, Oct 14, 2016 at 2:06 PM, Tony Kurc  wrote:
>> > > 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
>> > > successful.
>> > >
>> > > Tony
>> > >
>> > > On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora  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
>> > >>  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
>> > >>
>> >
>>
>
>

Re: Problem preparing to execute 0.7.1 release

[Tony Kurc]

Joe,
For 0.7.1, I'll take care of getting KEYS right in the release directory. I
believe that I (or another PMC member) can also perform the move to
release. It sounds like once I get the KEYS sorted, we're ready for a vote.

As for the perms on the dist directories, it sounds like we may have some
things to sort out before the next committer (and not PMC member) can do a
release, and we may need to update the docs.

Tony

On Sun, Oct 16, 2016 at 5:53 PM, Joe Skora  wrote:

> 1. I was able to perform the release as you expected and create the
> staging repository.  :-D
>
> 2. I have not sent the release vote email because the template states
> "KEYS file available here:https://dist.apache.org/
> repos/dist/release/nifi/KEYS" but my keys are not included there yet.
>
> 3. I contacted the INFRA team via HipChat and they said that normally only
> the PMC can commit to dist/*, but the PMC can extend the privilege to
> committers.  Thus, I should not have been able to commit to dist/dev
> either.  (I've attached a copy of the chat.)
>
> So it appears that unless permissions are specially granted, the release
> manager role does require PMC membership.
>
> How do you want to proceed?
>
> On Fri, Oct 14, 2016 at 5:09 PM, Tony Kurc  wrote:
>
>> Also, it looks like the difference between the KEYS file on dev and
>> release
>> prior to you adding your key to dev is that it looks like Joe Percivall's
>> key was sort of added twice to the release repo.
>>
>> dev KEYS before Joe Skora addition:
>>  https://dist.apache.org/repos/dist/dev/nifi/KEYS?p=14135
>>
>> release KEYS now :
>> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14117
>>
>> release KEYS before Joe Percivall addition (major difference is adding two
>> identical key blocks)
>> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14116
>>
>> We should tidy that up when the next release is ready.
>>
>>
>> On Fri, Oct 14, 2016 at 2:10 PM, Joe Witt  wrote:
>>
>> > I'm thinking the same thing Tony.  Joe you should be able to do the
>> > full process and we just might need to help with the final push of the
>> > official bits to the release directory.  In parallel please submit a
>> > request to INFRA on permissions for that folder.  Perhaps there is
>> > something else I need to activate though I'm not aware of anything.
>> >
>> > Thanks
>> > Joe
>> >
>> > On Fri, Oct 14, 2016 at 2:06 PM, Tony Kurc  wrote:
>> > > 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
>> > > successful.
>> > >
>> > > Tony
>> > >
>> > > On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora  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
>> > >>  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
>> > >>
>> >
>>
>
>

Re: Problem preparing to execute 0.7.1 release

[Joe Skora]

1. I was able to perform the release as you expected and create the staging
repository.  :-D

2. I have not sent the release vote email because the template states "KEYS
file available here:https://dist.apache.org/repos/dist/release/nifi/KEYS";
but my keys are not included there yet.

3. I contacted the INFRA team via HipChat and they said that normally only
the PMC can commit to dist/*, but the PMC can extend the privilege to
committers.  Thus, I should not have been able to commit to dist/dev
either.  (I've attached a copy of the chat.)

So it appears that unless permissions are specially granted, the release
manager role does require PMC membership.

How do you want to proceed?

On Fri, Oct 14, 2016 at 5:09 PM, Tony Kurc  wrote:

> Also, it looks like the difference between the KEYS file on dev and release
> prior to you adding your key to dev is that it looks like Joe Percivall's
> key was sort of added twice to the release repo.
>
> dev KEYS before Joe Skora addition:
>  https://dist.apache.org/repos/dist/dev/nifi/KEYS?p=14135
>
> release KEYS now :
> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14117
>
> release KEYS before Joe Percivall addition (major difference is adding two
> identical key blocks)
> https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14116
>
> We should tidy that up when the next release is ready.
>
>
> On Fri, Oct 14, 2016 at 2:10 PM, Joe Witt  wrote:
>
> > I'm thinking the same thing Tony.  Joe you should be able to do the
> > full process and we just might need to help with the final push of the
> > official bits to the release directory.  In parallel please submit a
> > request to INFRA on permissions for that folder.  Perhaps there is
> > something else I need to activate though I'm not aware of anything.
> >
> > Thanks
> > Joe
> >
> > On Fri, Oct 14, 2016 at 2:06 PM, Tony Kurc  wrote:
> > > 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
> > > successful.
> > >
> > > Tony
> > >
> > > On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora  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
> > >>  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
> > >>
> >
>
https://www.hipchat.com/gIjVtYcNy

 Sunday October 16, 2016 
[4:06 PM] Joseph Skora: I'm a committer on the Apache NiFi project.  In order 
to perform a release I am trying to add my keys to the project's KEYS file.I 
can commit to https://dist.apache.org/repos/dist/dev/nifi/ but receive 403 
errors committing to https://dist.apache.org/repos/dist/release/nifi/.What is 
the correct place to submit the request to get permissions on the release 
folder?  Or, is that something the PMC can correct?
[4:07 PM] SNMP2HipChat: SNMP Update: Issues detected with crius.apache.org. See 
the status page for more details.
[4:16 PM] JIRA: INFRA-12772: ASFBot enabled on #maven and #maven-dev
→Create Issue→Waiting for Infra
by Stephen Connolly.
[4:17 PM] Chris Lambertus (fluxo): @JosephSkoraGuest you'll need to work with 
your PMC on that
[4:19 PM] Gavin McDonald (McDuck): seems strange to me he can commit to /dev/ 
and not /release/
[4:20 PM] Gavin McDonald (McDuck): they are both the same perms, i..e pmc 
membership required
[4:23 PM] Joseph Skora: @gmcdonald The PMC thought that as a

Re: Problem preparing to execute 0.7.1 release

[Tony Kurc]

Also, it looks like the difference between the KEYS file on dev and release
prior to you adding your key to dev is that it looks like Joe Percivall's
key was sort of added twice to the release repo.

dev KEYS before Joe Skora addition:
 https://dist.apache.org/repos/dist/dev/nifi/KEYS?p=14135

release KEYS now :
https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14117

release KEYS before Joe Percivall addition (major difference is adding two
identical key blocks)
https://dist.apache.org/repos/dist/release/nifi/KEYS?p=14116

We should tidy that up when the next release is ready.


On Fri, Oct 14, 2016 at 2:10 PM, Joe Witt  wrote:

> I'm thinking the same thing Tony.  Joe you should be able to do the
> full process and we just might need to help with the final push of the
> official bits to the release directory.  In parallel please submit a
> request to INFRA on permissions for that folder.  Perhaps there is
> something else I need to activate though I'm not aware of anything.
>
> Thanks
> Joe
>
> On Fri, Oct 14, 2016 at 2:06 PM, Tony Kurc  wrote:
> > 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
> > successful.
> >
> > Tony
> >
> > On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora  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
> >>  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
> >>
>

Re: Problem preparing to execute 0.7.1 release

[Joe Witt]

I'm thinking the same thing Tony.  Joe you should be able to do the
full process and we just might need to help with the final push of the
official bits to the release directory.  In parallel please submit a
request to INFRA on permissions for that folder.  Perhaps there is
something else I need to activate though I'm not aware of anything.

Thanks
Joe

On Fri, Oct 14, 2016 at 2:06 PM, Tony Kurc  wrote:
> 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
> successful.
>
> Tony
>
> On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora  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
>>  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
>>

Re: Problem preparing to execute 0.7.1 release

[Tony Kurc]

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
successful.

Tony

On Fri, Oct 14, 2016 at 12:01 PM, Joe Skora  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
>  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
>