1138680 - Deploy Mercurial 3.3.2

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[Gregory Szorc [:gps]]

Mercurial 3.3.2 was released today. Per our production upgrade procedure, we start considering upgrades after the first point release after a major quarterly release. 3.3.2 is that first release (3.3.1 was scrubbed).

There is one known regression in 3.3 that concerns me: tags cache losing entries for filtered heads. I reported this issue upstream. Fortunately, it is only concerning on very large repositories that have both obsolescence enabled and many obsoleted heads. This shouldn't be relevant to hg.mozilla.org at this juncture. I'd rather get 3.3 on the server so we can start doing some cool stuff with hgweb (bugs to be filed or linked soon).

bkero: can you get an RPM built and added to our rpm server?

Comment 1

[Gregory Szorc [:gps]]

Deployment is tentatively scheduled for next Tuesday, March 10.

Comment 2

[Hal Wine [:hwine] use NI!]

Moved to Wednesday, March 11 (accidentally, but don't over-rotate) with notification:
  https://groups.google.com/d/msg/mozilla.dev.version-control/LfUyCPYLhWE/6u8ZpQ2HDH4J

Comment 3

[Gregory Szorc [:gps]]

This work is done.

There were a small handful of HTTP 500 errors served from hgweb1 because httpd wasn't restarted as part of the upgrade and when it was put back in the load balancer it had kind of a frankenstein software state. bkero was working on an ansible playbook for automating this deployment. So hopefully it won't happen next time.