I would have thought Kalyan had permission to update the KEYS file with his own key as he is a commiter on the project. Kalyan did you use the following:
svn co https://dist.apache.org/repos/dist/release/sentry ? I think a committer on the project should create the signed release by the way. Colm. On Mon, Jul 31, 2017 at 11:38 PM, Sergio Pena <sergio.p...@cloudera.com> wrote: > Hi PMC, > > I'm in the last step where I need to sign the tar.gz package. I already > created a GPG key and can sign the package. I worked with Kalyan offline to > try to include his key in the KEYS file (https://dist.apache.org/ > repos/dist/release/sentry/KEYS) in order to sign them with his key, but > he does not have permission either. > > I was investigating and seems this SVN repo is only writable for PMC > members?. I will need some PMC assistance now to continue with the release. > What can we do now? > > - Should I create a JIRA to include my GPG key into the KEYS file? is it > secure? > - Should I create a JIRA to include the signed .tar.gz? can someone do > this directly? > > Any other recommendations to continue with the release? > > - Sergio > > On Mon, Jul 10, 2017 at 9:46 AM, Sergio Pena <sergio.p...@cloudera.com> > wrote: > >> Great, I'm gonna go ahead and create an umbrella jira. I will take a look >> at the priority of those jiras meant for 1.8.0, and link them to the >> umbrella jira as blockers if they have to be there. >> >> On Mon, Jul 10, 2017 at 9:39 AM, Colm O hEigeartaigh <cohei...@apache.org >> > wrote: >> >>> +1 on going ahead with the release. However, first I'd like to see some >>> work done on clearing up what the remaining tasks are for the release. In >>> JIRA, there are currently 11 issues "in progress" and 59 issues "to do" >>> for >>> 1.8.0: >>> >>> https://issues.apache.org/jira/projects/SENTRY/versions/12335076 >>> >>> Colm. >>> >>> >>> On Fri, Jul 7, 2017 at 10:32 PM, Kalyan Kumar Kalvagadda < >>> kkal...@cloudera.com> wrote: >>> >>> > I will make some time to help Sergio in this regard. :-) >>> > >>> > -Kalyan >>> > >>> > On Fri, Jul 7, 2017 at 4:28 PM, Alexander Kolbasov <ak...@cloudera.com >>> > >>> > wrote: >>> > >>> > > Sergio, thanks for stepping up. >>> > > >>> > > We'll figure out something to get things moving. Hopefully Kalyan >>> will >>> > have >>> > > some time to do any required commits otherwise someone else will >>> step in. >>> > > Please go ahead and start the process. >>> > > >>> > > - Alex >>> > > >>> > > On Fri, Jul 7, 2017 at 11:11 PM, Sergio Pena < >>> sergio.p...@cloudera.com> >>> > > wrote: >>> > > >>> > > > Hi, >>> > > > >>> > > > It's been a while since the discussion for release 1.8.0 passed >>> and it >>> > > > hasn't happened yet. I understand that people are busy, especially >>> PMC >>> > > and >>> > > > committers, to do a release; so I would like to volunteer to help >>> and >>> > > > coordinate the 1.8.0 release. >>> > > > >>> > > > I'm not a committer, and doing a release requires committer >>> status, so >>> > I >>> > > > was wondering if the rest of the community would like to help me on >>> > doing >>> > > > this release, perhaps by only doing those tasks that require commit >>> > > > permissions, such as branch creation and sign/upload artifacts, >>> and of >>> > > > course the review of patches for documentation and change of >>> versions. >>> > > > >>> > > > Kalyan (who volunteered on the 1.8.0 release) has been busy and he >>> > agreed >>> > > > that I could help him on doing this release. >>> > > > >>> > > > Any thoughts on this? >>> > > > I would like to start the release process next week. >>> > > > >>> > > > - Sergio >>> > > > >>> > > >>> > >>> >>> >>> >>> -- >>> Colm O hEigeartaigh >>> >>> Talend Community Coder >>> http://coders.talend.com >>> >> >> > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
