config/milestone.txt
author Nathan Froyd <froydnj@mozilla.com>
Thu, 11 Apr 2013 16:57:54 -0400
changeset 128513 ebcfc07b631511d2a5c9bd52abbe2ff76428a10f
parent 126868 aae004a3c5d9771fa4c8ee9c70ea274cc7623ee3
child 131803 ec5790a0e0a261ac1646ae2e99aa520d2fdb4cec
permissions -rw-r--r--
Bug 860860 - followup: fix json.dump call and be more explicit about object ordering; r=gps It turns out the simple s/simplejson/json/ didn't work because build_tooltool_manifest used item_sort_key to ensure that the objects read in were written out in the same order. This scheme was brittle, since it only understand a couple of keys from the manifest file, and it doesn't work with the stdlib json. Instead, use object_pairs_hook=collections.OrderedDict with json.load, which ensures that current objects get written out in the same order they were read in *and* that any future keys will be handled automagically. DONTBUILD because NPOTB

# Holds the current milestone.
# Should be in the format of
#
#    x.x.x
#    x.x.x.x
#    x.x.x+
#
# Referenced by milestone.pl.
# Hopefully I'll be able to automate replacement of *all*
# hardcoded milestones in the tree from these two files.
#--------------------------------------------------------

23.0a1