623787 - please create hg.mozilla.org/addon-sdk

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Brian Warner [:warner :bwarner]]

We're fixing up the "Add-On SDK" (formerly known as "Jetpack") repository
layout. We've switched the primary repository over to git and github, but we
need to make the code available via HG for the sake of automated testing by
RelEng.

Jetpack (back when it natively lived in HG) was first made available at
hg.mozilla.org/labs/jetpack-sdk . When we moved over to git, I wrote a bridge
script that copied revisions from git into hg and published it to this same
repository. In mid-December, when we first started using git branches, a
problem with this bridge resulted in a hard-to-resolve "multiple head"
getting pushed into the labs/jetpack-sdk HG repo, and the bridge has been
stuck ever since (Bug 618838). I've figured out how to resolve the problem,
and have written a new bridge script, but the resulting HG repo is completely
different, and shares no revisions in common with the old one.

In addition, the project has been renamed "Add-On SDK", and has moved out of
Mozilla Labs.

So, to resolve both problems in a single bound, we'd like to:

* create http://hg.mozilla.org/addon-sdk
* delete http://hg.mozilla.org/labs/jetpack-sdk

after which I can start the bridge script running and populate the new
"addon-sdk" HG repo with the proper contents.

I know it's a bit weird to delete an HG repo. It'd probably be a good idea to
leave a note of some sort there so that folks can find the new one. I don't
think a real HTTP Redirect would be appropriate, because the new repo will
not share history with the old one, and anybody with an old checkout that
tries to update it should not automatically be given revisions from the new
one.

Comment 1

[Aravind Gottipati [:aravind]]

Could you make this a project repo?  like hg.m.o/projects/addon-sdk ?  Does it need to be a top level repo?

Also, regarding deleting the old repo.. how about I just change its description to say the repo is now obsolete and point people to the new one?

Comment 2

[Brian Warner [:warner :bwarner]]

I think changing the description ought to be sufficient. Ideally anyone who pulls from it would get a note telling them about the change, but I don't know if hg's remote-pull protocol has a feature for that.

I'll let Myk answer about the repo name.. I know it's no longer a Labs thing, but I don't know what other top-level project name would be appropriate.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

(In reply to comment #1)
> Could you make this a project repo?  like hg.m.o/projects/addon-sdk ?  Does it
> need to be a top level repo?

Yes, it can be hg.m.o/projects/addon-sdk (although Add-on SDK is a product, not a project; Jetpack is the project producing that product; but for repository location purposes, /projects/ should be fine).

Comment 4

[Aravind Gottipati [:aravind]]

Repository created, added a description to jetpack-sdk indicating it's now obsolete.

Made the addon-sdk repo a level_2 repo.  Please let me know if you want it changed to something else.