965330 - Create new unified repository for version control hooks and extensions

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Gregory Szorc [:gps]]

A few months ago, I contacted (hopefully) everyone who has written Mercurial hooks and extensions tailored towards Mozilla development and proposed that we create a new, unified repository to hold all the source code. I'd like to request we do that now.

To summarize, today we have a handful of separate repositories containing "version control support" files. There's a lot of potential for sharing functionality and for making the landscape more easily understood and changeable. Having a unified repository will enable this cohesion and hopefully lower maintenance costs.

I'd like to get to a state where things like the Mercurial server hooks as well as optional client extensions are present in this repo. The deployment process for hg.mozilla.org would simply be to |hg pull -u| this repo. This means some eventual refactoring of our IT setup. That's not in scope for right now. I imagine that in the short term this repository will aggregate extensions. Over time, we can start rolling IT over to it.

I think the hardest part of this bug is deciding a name and location on hg.mozilla.org. If we go with Mercurial-specific, hgcustom/moz-hg might be a good choice. If we want Git in scope, we could do /moz-versioncontrol-tools, /versioncontrol-tools or something.

Let's have a few days to bikeshed the name then let's create this sucker.

Comment 1

[Ed Morley [:emorley]]

Apart from presumably {bzexport,qimportbz,qbackout} what other existing extensions/tools/repos would you suggest including in this new repository?

Comment 2

[Gregory Szorc [:gps]]

https://hg.mozilla.org/users/gszorc_mozilla.com/hgext-gecko-dev

One of the trychooser ones (let's unify them already).

Eventually pushlog.

We'd probably throw a copy of https://bitbucket.org/indygreg/python-mozautomation in there.

I've wanted to write a small extension that ignores *RELBRANCH bookmarks on pull.

It looks like we'll have a small extension in bug 962300.

Comment 3

[Gregory Szorc [:gps]]

Nobody responded. Let's create hg.mozilla.org/version-control-tools with the description "Mozilla version control infrastructure and customizations to version control tools."

Comment 4

[Kendall Libby [:fubar] (he/him)]

Pinging Hal for repo name sign off. What hooks/permissions?

Comment 5

[Gregory Szorc [:gps]]

Level 2 access. We don't need any hooks right now, I think. There's likely going to be a lot of initial turmoil to get the repo in order. We can add hooks later.

Comment 6

[hwine]

(In reply to Gregory Szorc [:gps] from comment #3)
> Nobody responded. Let's create hg.mozilla.org/version-control-tools with the
> description "Mozilla version control infrastructure and customizations to
> version control tools."

We really shouldn't create any top level repositories for a number of reasons.

This looks like a good fit to go under http://hg.mozilla.org/hgcustom

Greg - any objections?

Comment 7

[Gregory Szorc [:gps]]

I'm fine with hgcustom. It's just a URL. We can move the repo any time, really. Who knows, maybe one day we'll import the SSH and HTTP hosting scripts into this repo and we'll provide a facility for mapping repos to new URLs transparently :)

Comment 8

[Kendall Libby [:fubar] (he/him)]

Done.  http://hg.mozilla.org/hgcustom/version-control-tools/

Comment 9

[Gregory Szorc [:gps]]

I can confirm the repo is working as intended. I even blogged about it:

http://gregoryszorc.com/blog/2014/02/05/new-repository-for-mozilla-version-control-tools/

Thanks for the quick work!

Now, to file a gazillion bugs to make this thing useful...