The releases should absolutely be tagged with "rel/release-X.Y.Z". The tag should be signed with a personal key in https://people.apache.org/keys/group/ranger.asc that is signed by at least one well connected Apache member.
.. Owen On Wed, Dec 28, 2016 at 4:12 PM, Lal,Alok(allal) <al...@ebay.com> wrote: > Sorry about the prior garbled message. > > > > @Vel, @Bosco, > > 1. Allow me to make that change. I can add a note after “Publish > binary release in Maven” in “Post Release Tasks” as at that point one has > ready access to the sha1. Does that sound right? > > 2. I could push the tags retroactively based on the published > sources in release archive > <http://archive.apache.org/dist/incubator/ranger/>. But I can’t think of > a reliable way to do that. The best I could come up with was as follows: > find out the last “release candidate” tag for a release and copy that tag a > “release” tag. > > a. For example for 0.4 the last rc tag was “ranger-0.4.0-rc3” on > 02d0f71 so I’d push another tag named “ranger-0.4” for 02d0f71. > > b. Do we want to do that? If so, is there a more reliable way to > ascertain the sha1 of what was released to the repo? Relying on “last rc > tag being correct” seems reasonable but is there some hint in the released > source of the sha1 that it was exported from? > > c. Also from some releases like 4.1 there isn’t anything in the > repository. Perhaps that means it was never 4.1 was never released? I’d > leave those out – treat artifacts in the archive as the source of truth for > determining which releases have been made. > > > > > > > > *From: *"Lal,Alok(allal)" <al...@ebay.com> > *Date: *Wednesday, December 28, 2016 at 10:34 AM > *To: *"user@ranger.incubator.apache.org" <user@ranger.incubator.apache.org > > > *Subject: *Re: Git tags for releases > > > > *From: *Don Bosco Durai <bo...@apache.org> > *Reply-To: *"user@ranger.incubator.apache.org" < > user@ranger.incubator.apache.org> > *Date: *Tuesday, December 27, 2016 at 5:02 PM > *To: *"user@ranger.incubator.apache.org" <user@ranger.incubator.apache.org > > > *Subject: *Re: Git tags for releases > > > > We should be able to do this. > > > > Vel, can we can make this part of our post-release checklist? > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65867946 > > > > Thanks > > > > Bosco > > > > > > *From: *Lars Francke <lars.fran...@gmail.com> > *Reply-To: *<user@ranger.incubator.apache.org> > *Date: *Tuesday, October 18, 2016 at 5:55 AM > *To: *<user@ranger.incubator.apache.org> > *Subject: *Git tags for releases > > > > Hi, > > > > I've looked at git and there are some tags for RCs but I can't find any > git tags for releases. I assume this is by accident. Would you mind adding > them? Makes it easier to find the specific commit that a release was based > on. > > > > Thank you! > > > > Cheers, > > Lars > > >
