back out b28237b05041 and 62d307141ca5 - back to nightly signing
authorAki Sasaki <asasaki@mozilla.com>
Tue, 08 Aug 2017 13:33:56 -0700
changeset 654129 de17a3f6540fccf7746ed080b3ce10c7b4acfc88
parent 654128 2dacc9697ce74b8dec0b026f12ef00124f813aa2
child 654130 1fb9695c534d09a55b8801b83432d5d7564bdbad
push id76486
push userbmo:jlorenzo@mozilla.com
push dateMon, 28 Aug 2017 09:42:17 +0000
milestone57.0a1
backs outb28237b050414322c824aa40e8a0b44b0e5f3216
back out b28237b05041 and 62d307141ca5 - back to nightly signing MozReview-Commit-ID: A08WyM07l90
README.txt
taskcluster/taskgraph/util/scriptworker.py
--- a/README.txt
+++ b/README.txt
@@ -20,9 +20,8 @@ are accessible on Google Groups, or news
 
 You can download nightly development builds from the Mozilla FTP server.
 Keep in mind that nightly builds, which are used by Mozilla developers for
 testing, may be buggy. Firefox nightlies, for example, can be found at:
 
     https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
             - or -
     https://nightly.mozilla.org/
-
--- a/taskcluster/taskgraph/util/scriptworker.py
+++ b/taskcluster/taskgraph/util/scriptworker.py
@@ -35,17 +35,17 @@ nuance so certain m-b and m-r tasks use 
 release sign when we have a signed-off set of candidate builds.  This current
 approach works for now, though.
 
 This is a list of list-pairs, for ordering.
 """
 SIGNING_SCOPE_ALIAS_TO_PROJECT = [[
     'all-nightly-branches', set([
         'mozilla-central',
-#        'date',
+        'date',
     ])
 ], [
     'all-release-branches', set([
         'mozilla-beta',
         'mozilla-release',
     ])
 ]]