679077 - switch release automation release notes URLs to mozilla.org after One Mozilla transition

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Other, defect, P3)

Description

[[e-mail] (:bhearsum)]

After the mozilla.com/mozilla.org merge happens we'll need to switch the release automation to point at mozillla.org for release notes. We don't need to update old links, they'll be seamlessly redirected.

mxr shows a few places that probably need updates:
buildbot-configs/mozilla/release-firefox-mozilla-1.9.2.py
buildbot-configs/mozilla/release-firefox-mozilla-1.9.1.py
buildbot-configs/mozilla/staging_release-firefox-mozilla-1.9.2.py
tools/release/signing/Makefile
tools/release/signing/sign-release.py
tools/release/patcher-config-bump.pl
tools/lib/perl/Release/Patcher/Config.pm
mozharness/test/test_script.py

Comment 1

[[e-mail] (:bhearsum)]

Mass move of bugs to Release Automation component.

Comment 2

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum [:bhearsum] from comment #0)
> After the mozilla.com/mozilla.org merge happens we'll need to switch the
> release automation to point at mozillla.org for release notes. We don't need
> to update old links, they'll be seamlessly redirected.
> 
> mxr shows a few places that probably need updates:
> buildbot-configs/mozilla/release-firefox-mozilla-1.9.2.py
> buildbot-configs/mozilla/release-firefox-mozilla-1.9.1.py
> buildbot-configs/mozilla/staging_release-firefox-mozilla-1.9.2.py
> tools/release/signing/Makefile
> tools/release/signing/sign-release.py
> tools/release/patcher-config-bump.pl
> tools/lib/perl/Release/Patcher/Config.pm
> mozharness/test/test_script.py

A bunch of these are dead now. New list is:
/mozharness/test/networked/test_base_script.py
/mozharness/test/test_base_script.py
/tools/lib/perl/Release/Patcher/Config.pm
/tools/lib/python/signing/utils.py
/tools/release/signing/Makefile
/tools/release/patcher-config-bump.pl
/tools/release/patcher-configs/mozBeta-branch-patcher2.cfg
/tools/release/patcher-configs/mozRelease-branch-patcher2.cfg
/tools/release/patcher-configs/mozEsr10-branch-patcher2.cfg

Comment 3

[Lawrence Mandel [:lmandel] (use needinfo)]

Is there anything left to do here?

Comment 4

[[e-mail] (:bhearsum)]

(In reply to Lawrence Mandel [:lmandel] from comment #3)
> Is there anything left to do here?

Kindof. We're still pointing release notes to www.mozilla.com (eg in https://aus3.mozilla.org/update/3/Firefox/16.0.2/20121024073032/WINNT_x86-msvc/de/release/default/default/default/update.xml?force=1). I've been putting this off while we transition to Balrog, because it's harder to verify that Balrog is doing the right thing if we change things like this mid-testing.

Comment 5

[[e-mail] (:bhearsum)]

We'll make this change (finally) after we switch to Balrog, which is expected to happen in mid-January.

Comment 6

[[e-mail] (:bhearsum)]

Attachment: switch product details to mozilla.org

I'm pretty sure this is the only thing that needs updating. Old signing is dead. The mozharness scripts from the earlier comment aren't relevant, and the patcher configs will be updated with next releases.

Comment 7

[[e-mail] (:bhearsum)]

All future releases should use mozilla.org instead of mozilla.com now.