----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/42117/#review113655 -----------------------------------------------------------
build-support/release/release (line 137) <https://reviews.apache.org/r/42117/#comment174414> IIUC, this commit will be pushed and reachable from the tag, but not from master. Even if thats not right its not clear to me what branching above helps. build-support/release/release (line 140) <https://reviews.apache.org/r/42117/#comment174415> No longer true. - John Sirois On Jan. 10, 2016, 11:26 a.m., Bill Farner wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/42117/ > ----------------------------------------------------------- > > (Updated Jan. 10, 2016, 11:26 a.m.) > > > Review request for Aurora, John Sirois and Zameer Manji. > > > Repository: aurora > > > Description > ------- > > This is in response to the e-mail below regarding git server-side policy > enforcement rendering `rel/` tags immutable. > > ``` > Greeting PMCs: > (bcc to p...@apache.org) > > Following direction from the Board, Infrastructure has modified git to > permit force pushes, and branch/tag deletion. > > In accordance with the guidance that the Board we've implemented a few > changes you should be aware of: > > First, If a forced commit is pushed, the subsequent commit email will > contain '[Forced Update!]' in the subject line. The hope here is that > it draws extra attention to the situation for a project community to > be aware, and take appropriate action if needed. > > Second, we've changed the 'protected' portions of git to primarily > focus on refs/tags/rel - thus any tags under rel, will have their > entire commit history. This provides the provenance that the ASF needs > for releases, while still giving projects the ability to mold their > repository in the way they see fit. > > Thus when a release vote is successful - part of the release process > should become tagging the voted upon commit SHA under rel/ to make it > indelible. ('# git tag rel/v15.4.2 ' or something similar.) > > > If you have questions, please feel free to email infrastruct...@apache.org > > > --David > on behalf of Apache Infrastructure > ``` > > > Diffs > ----- > > build-support/release/release 9e8dd41209b8d687974d1cdc731c945afab3946e > > Diff: https://reviews.apache.org/r/42117/diff/ > > > Testing > ------- > > > Thanks, > > Bill Farner > >
