Pushing tag attached to non-pushed commit shouldn't be allowed
Submitted by Bastien Nocera
Assigned to Release Engineering People
Managed to make a pig's ear out of the gnome-control-center 3.4.3 release.
The object tagged is: http://git.gnome.org/browse/gnome-control-center/tag/?h=gnome-3-4&id=GNOME_CONTROL_CENTER_3_4_3 for which the parent is: http://git.gnome.org/browse/gnome-control-center/commit/?h=gnome-3-4&id=b3f5f677348be4c45665159fa7dc3e3c0892cb43
I was allowed to create the tag locally, push it to the repo, change the order of 2 unpushed changes locally (the tag was against the one-before-last commit, which became the last commit) and push those re-ordered changes to the repo.
It would be great if we standardised tags or commit messages to ensure that releases exist in the repo before ftpadmin will allow installation.