843381 - Create hg repo for NSS

Status: RESOLVED DUPLICATE of bug 844385

(Release Engineering :: General, defect)

Description

[Chris Cooper [:coop] (he/him)]

Initial work for moving NSS from CVS->hg will happen in a user repo/project branch, but *eventually* it will need a repo of its own.

This is a placeholder bug until that initial work is done.

Comment 1

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

I rented the following two project trees:

NSPR: https://hg.mozilla.org/projects/fig/ 
NSS:  https://hg.mozilla.org/projects/gum/ 

Both are empty, which is how we want them. I did not rent trees for nss-python or JSS. Those should be easy to get working later and I think we should concentrate on NSPR and NSS for now.

I understand that we need to work with RelEng to configure which tests need to be run. We're supposed to file a separate bug for that, according to the wiki. But, I think this is a particularly special case so I'm not even sure what to request; consequently, I didn't file the bug.

See https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches#Enabling.2FDisabling_of_platforms.2C_tests.2C_nightly_updates

Comment 2

[Chris Cooper [:coop] (he/him)]

Brian: I'm marking this as a dupe of bug 844385 because that's where the actual repo creation happened. Please feel free to re-open and morph if you need somewhere to track your NSS work on the project branches.

Comment 3

[Kaspar]

(In reply to Chris Cooper [:coop] from comment #2)
> Brian: I'm marking this as a dupe of bug 844385 because that's where the

Bug 844385 is hidden, so I'm adding the comment here: after the migration to hg, commit notices are no longer sent to https://lists.mozilla.org/listinfo/dev-tech-crypto-checkins. Can this be re-enabled for the hg commits?

Comment 4

[Kai Engert [:KaiE:]]

(In reply to Kaspar Brand from comment #3)
> after the migration to
> hg, commit notices are no longer sent to
> https://lists.mozilla.org/listinfo/dev-tech-crypto-checkins. Can this be
> re-enabled for the hg commits?

That's tracked in bug 846395.