On 10/9/14 1:31 PM, Chris Friesen wrote:
On 10/09/2014 08:12 AM, Jeremy Stanley wrote:
On 2014-09-30 01:38:29 +0000 (+0000), Jeremy Stanley wrote:
the tips of these branches have been tagged "havana-eol" in
preparation for branch deletion. The list of affected Git
repositories is as follows:
Just following up to note that I finally removed the stable/havana
branches of the above mentioned projects, in accordance with the EOL
announcement from a couple weeks ago.
Just curious...why do we remove the stable branches for old releases? Is the idea to force people onto new branches?
If I'm not mistaken; it appears the tag rename from "havana" -> "havana-eol" may be effecting the upgrade CI tests in recent commits (ex: ).
For example in real-db-upgradenovamysql_user001:th-mysql:
2014-10-09 17:12:11,771 [output] Database is from Grizzly! Upgrade via Havana
2014-10-09 17:12:11,774 [output] error: branch 'stable/havana' not found.
2014-10-09 17:12:11,784 [output] Fetching origin
2014-10-09 17:12:16,634 [output] Switched to a new branch 'stable/havana'
2014-10-09 17:12:16,639 [output] fatal: ambiguous argument 'remotes/origin/stable/havana': unknown revision or path not in the working tree.