I have made new refs in rel/ pointing to the same SHA as the earlier tag and pushed them.
I don't believe any committers have or are planning to make PGP signed commits. I also made a quick check with 'git log' of recent release refs and did not find signed commits. That is a practice we could adopt. I'd be supportive of that. All committers would need to do so to make it worthwhile. On Mon, Jan 25, 2016 at 3:01 PM, Sean Busbey <[email protected]> wrote: > one question: will the new historic tags have your PGP signature rather > than the original RM(s)? If so, do we need to make a note of the cause of > this discrepancy? > > A vote in favor of leaving the old tags: since we've been treating release > tags as permalinks (regardless of their actual mutable state), folks are > likely to have links to them saved places. > > On Mon, Jan 25, 2016 at 3:26 PM, Andrew Purtell <[email protected]> > wrote: > > > Question: Would you like me to clean up afterward by pushing deletes for > > the soon-to-be duplicate release tags? No rush on an answer. I'll wait a > > few days for responses to come in. > > > > On Mon, Jan 25, 2016 at 1:24 PM, Andrew Purtell <[email protected]> > > wrote: > > > > > I'll be adding tags under refs/rel/ for all previous HBase releases > > today, > > > using a snapshot of HBase's Apache git repository last updated at > Monday > > > January 25 13:20:47 PST 2016. > > > > > > -- > > > Best regards, > > > > > > - Andy > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein > > > (via Tom White) > > > > > > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > > > > -- > Sean > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
