tl;dr: release tags are changing to the format rel/0.11.0. no more release branches.
Recent changes to configuration of Apache's git server have added protections to tags prefixed by rel/. We are going to take advantage of this so that our release tags are immutable on the git server. Since the same protections do not apply for branches, i will be deleting old release branches and we will not create them for the foreseeable future. I have two patches to our release scripts that enact this change: https://reviews.apache.org/r/42117/ https://reviews.apache.org/r/42145/ For additional context, please see the infra e-mail below. Cheers, Bill From: David Nalley <ke4...@apache.org> > Date: Sun, 10 Jan 2016 13:00:04 -0500 > Subject: Git status update > To: "infrastruct...@apache.org" <infrastruct...@apache.org> > > 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 >
