771614 - Need a dxr-stable repo under hg.mozilla.org/projects

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Malini Das [:mdas] - Away, not checking bugmail]

We're making an hg mirror of a github branch (https://github.com/mozilla/dxr, stable branch). We'll need the mirror so releng can track it. I propose the name 'dxr-stable'

This mirror will be up for the forseeable future, since the DXR project has no plans to migrate to hg. Please let me know if you need any additional information.

Comment 1

[Reed Loden [:reed]]

Why don't you just use the existing https://hg.mozilla.org/webtools/dxr/ ?

Comment 2

[Malini Das [:mdas] - Away, not checking bugmail]

Jcranmer, would you be okay with using the webtools/dxr repo as the stable dxr hg mirror?

Comment 3

[Joshua Cranmer [:jcranmer]]

(In reply to Malini Das [:mdas] from comment #2)
> Jcranmer, would you be okay with using the webtools/dxr repo as the stable
> dxr hg mirror?

I'd be fine so long as we wipe what's already there and replace it with a proper git clone.

Comment 4

[Shyam Mani [:fox2mike]]

Not sure if we're okay to wipe this completely. Releng takes a call on existence of repos.

Comment 5

[Justin Wood (:Callek)]

(In reply to Joshua Cranmer [:jcranmer] from comment #3)
> (In reply to Malini Das [:mdas] from comment #2)
> > Jcranmer, would you be okay with using the webtools/dxr repo as the stable
> > dxr hg mirror?
> 
> I'd be fine so long as we wipe what's already there and replace it with a
> proper git clone.

Point of information, question, Do we lose history relating to dxr if we wipe this out, or is the full history from this repo present in the current github copy?

Comment 6

[Joshua Cranmer [:jcranmer]]

(In reply to Justin Wood (:Callek) from comment #5)
> (In reply to Joshua Cranmer [:jcranmer] from comment #3)
> > (In reply to Malini Das [:mdas] from comment #2)
> > > Jcranmer, would you be okay with using the webtools/dxr repo as the stable
> > > dxr hg mirror?
> > 
> > I'd be fine so long as we wipe what's already there and replace it with a
> > proper git clone.
> 
> Point of information, question, Do we lose history relating to dxr if we
> wipe this out, or is the full history from this repo present in the current
> github copy?

The github copy was created from pushing the original hg copy via hg-git. After that, I used the git copy to push back to hg, but this involved a lot of rebasing and I screwed something up on one of the reimports without realizing it. The only thing that the hg copy has that the git doesn't have (to my knowledge) is the DXR_CLANG_ALPHA* tags.

Comment 7

[Hal Wine [:hwine] use NI!]

(In reply to Shyam Mani [:fox2mike] from comment #4)
> Not sure if we're okay to wipe this completely. Releng takes a call on
> existence of repos.

Since we're talking about potentially wiping history, I'd like to get signoff from the original requester of the repo. That was :taras in bug 500863

The other alternative is to use a different name for the new repo to avoid confusion.

Comment 8

[Justin Wood (:Callek)]

(In reply to Hal Wine [:hwine] from comment #7)
> (In reply to Shyam Mani [:fox2mike] from comment #4)
> > Not sure if we're okay to wipe this completely. Releng takes a call on
> > existence of repos.
> 
> Since we're talking about potentially wiping history, I'd like to get
> signoff from the original requester of the repo. That was :taras in bug
> 500863
> 
> The other alternative is to use a different name for the new repo to avoid
> confusion.

(In reply to Joshua Cranmer [:jcranmer] from comment #6)
> The github copy was created from pushing the original hg copy via hg-git.
> After that, I used the git copy to push back to hg, but this involved a lot
> of rebasing and I screwed something up on one of the reimports without
> realizing it. The only thing that the hg copy has that the git doesn't have
> (to my knowledge) is the DXR_CLANG_ALPHA* tags.

Given Joshua's comments about history, I'd be inclined to suggest that nothing of real value is being lost, but I'll let taras chime in.

Comment 9

[Malini Das [:mdas] - Away, not checking bugmail]

According to Jonas, master will be treated as stable, and a testing repository would be ideal. So we'll need to either create a repo called dxr-testing, or we can use https://hg.mozilla.org/webtools/dxr/ provided that taras agrees.

Comment 10

[(dormant account)]

(In reply to Malini Das [:mdas] from comment #9)
> According to Jonas, master will be treated as stable, and a testing
> repository would be ideal. So we'll need to either create a repo called
> dxr-testing, or we can use https://hg.mozilla.org/webtools/dxr/ provided
> that taras agrees.

I agree with replacing https://hg.mozilla.org/webtools/dxr/ with new dxr code.

Comment 11

[Hal Wine [:hwine] use NI!]

fine by releng - back to dev services for implementation

Comment 12

[Shyam Mani [:fox2mike]]

Haha, okay. So now can someone let me know what exactly we need to do?

Comment 13

[Malini Das [:mdas] - Away, not checking bugmail]

(In reply to Shyam Mani [:fox2mike] from comment #12)
> Haha, okay. So now can someone let me know what exactly we need to do?

Wipe the https://hg.mozilla.org/webtools/dxr/ repository please!

Comment 14

[Shyam Mani [:fox2mike]]

Done and a shiny new scm_level_2 repo is in it's place.