1055304 - Provide a compatibility server to 'cloud-try' so legacy clients can push to it without any extensions

Status: RESOLVED INVALID

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

Comment 1

[Gregory Szorc [:gps]]

My vote is WONTFIX. Supporting cloud-try involves installing an extension, likely from version-control-tools. We shouldn't be afraid of asking people to do this.

The hardest part here is getting the Mercurial version compatibility right. We're shipping 3.0.2 in MozillaBuild. ReviewBoard requires 3.0 because supporting 2.9 and earlier would be a bit more painful given refactorings inside Mercurial. The same logic holds for cloud-try.

Installing Mercurial in userland is literally 1) download tarball of release 2) uncompress 3) make install PREFIX=/home/gps.

If nothing else, forced upgrading provides a great way to ensure people are having the fastest, most bug-free Mercurial experience possible.

I would target Mercurial 3.0+ and deprecate the try server/repo after a flag day.

Comment 2

[(dormant account)]

(In reply to Gregory Szorc [:gps] from comment #1)
> My vote is WONTFIX. Supporting cloud-try involves installing an extension,
> likely from version-control-tools. We shouldn't be afraid of asking people
> to do this.

That's my general feeling too. But lets keep this option on the table until we are sure the extension workflow is sufficiently free of papercuts.

Comment 3

[Mike Hommey [:glandium]]

Except not everyone uses mercurial to push to try...

Comment 4

[Gregory Szorc [:gps]]

(In reply to Mike Hommey [:glandium] from comment #3)
> Except not everyone uses mercurial to push to try...

Mercurial is involved at some step of the process, even for Git users.

Comment 5

[Gregory Szorc [:gps]]

We'll support pushing to headless try without an extension.