On 12/04/16 17:32, Ralph Giles wrote:
On Tue, Apr 12, 2016 at 3:51 AM, Neil Harris wrote:
for example, http://releases.mozilla.org/pub/firefox/releases/45.0.1/
Also note that the releases.mozilla.org host supports https, which
offers an additional verification path.
-r
Yes, indeed it do
On Tue, Apr 12, 2016 at 3:51 AM, Neil Harris wrote:
> for example, http://releases.mozilla.org/pub/firefox/releases/45.0.1/
Also note that the releases.mozilla.org host supports https, which
offers an additional verification path.
-r
___
dev-platform
This was a mistake on my part. The last release had some problems in
automation due to issues with our infrastructure
(https://bugzilla.mozilla.org/show_bug.cgi?id=1263082). As a result I had to
run some jobs manually and ran the checksums job in the wrong order so they
were not copied over
I'm not sure if this is the right list for this, but I thought I'd
better bring this to your attention.
Previous release directories have carried checksum files, with
signatures and a key file that allows the various binary files to be
validated. See, for example,
http://releases.mozilla.org/
4 matches
Mail list logo
