Updates for v0.10

[saivann]

Live preview: http://dg4.dtrt.org/en/download

Diff of formatting-only changes to the release notes: http://dg4.dtrt.org/diff.html
(diff will not be part of actual site)

• Release notes may need to be updated if they have changed after Bitcoin Core commit bitcoin/bitcoin@327d3e8 (Feburary 9th)
• _releases/2015-02-16-v0.10.0.md needs to be renamed with the right UTC date on the day of the release.
• A .torrent file should be automatically created in the bin/0.10.0 directory once the binaries are uploaded. Convert that .torrent link into a magnet link using a tool like transmission-show -m "bitcoin-0.10.0.torrent" and add that magnet URI needs to the YAML header of the file above: magnetlink: ... (a commented-out example is provided). This is optional because it can be done after this is merged (@harding is planning on doing it).
• Check the links. Especially check the link for the Mac OSX .dmg, as that frequently changes. If any links are broken, edit the file _templates/download.html (the OSX link is currently set to the same as used in RC4, with a commented-out example on line 12 of the download template providing the common alternative link)

Feel free to PM harding on Freenode to make the above changes when the release is near.

This pull request makes required changes to the download page for v0.10.0 and all texts refering to the long synchronization time. It should be merged when v0.10.0 is released.

Changes in this pull request:

• Set filenames once in the download page
• Edit download page for new or updated files
• Add link to the source code, GitHub and torrent download
• Edit: Replace long sync instructions by short instructions to run a full node on the download page

[harding]

I'm not sure we should "drop mentions of long sync time everywhere." The headers-first speed-up is immense---but only from the relative standpoint of how long it takes to sync older nodes.

Even on high-bandwidth connections, headers-first still takes two or more hours to verify the block chain. (It took about 4 hours on my laptop while I did other things and 6 hours on a two-core VPS.) Two, four, or six hours is a long wait by most people's standards. (Although I'm sure they're as appreciative as I am about not having to wait days.)

Maybe notesync should say something like: "Bitcoin Core synchronization will need to download and process data for a few hours." And maybe synctxt1 should be reverted to its previous text or mention that hours are required.

[saivann]

@harding I was assuming a higher performance improvement but indeed wrote these texts with uncertainty. Thanks for your testing! I will revert most of the changes in translations tomorrow.

[gmaxwell]

Current time to sync is less time than it took on the same hardware in mid 2011. I'm not sure what expectation you have here.

[saivann]

I am actually guilty of not reading enough about it and would have tested
it before the release if the pull req didn't get comments. I was simply not
sure if the wallet would be temporarily in SPV mode right after downloading
headers, and usable before full synchronization was completed.

Anyway, this improvement is massive, I just wanted to be sure we didn't
discourage users with outdated texts if we didn't have to.

[saivann]

I have just updated texts about the synchronization time.

[harding]

@saivann I'm going to update this branch today with the latest release notes. I just wanted to let you know since you usually force-push your updates. :-)

[harding]

The ready-to-merge release notes have been updated to those included in RC4 and I've updated @saivann's description of the PR with new preview links and a slightly expanded merge checklist. I'll keep that post updated with the latest information about this PR.

[harding]

@laanwj I've just updated this and it should be ready to merge. I've placed a checklist in @saivann's original description of this PR (the top post).

The only thing I'm worried about is the OSX .dmg link---the file name used in RC4 (bitcoin-0.10.0*.dmg) was not the one Saïvann expected (bitcoin-0.10.0-osx.dmg`). I've set the name in this PR to use the format from RC4, but I also added a commented-out variable in the file restoring the link back to the one Saïvann expected. Instructions are in the checklist

I'm heading to bed now, but I wrote an every-minute shell loop to sound an alarm when you upload the binaries, so hopefully I should be available to fixup this commit if necessary.

Edit: re-updated 2015-02-16 00:15 UTC. Still ready to merge.

[harding]

@laanwj I see the uploads have been made. Updating and testing this now, and I'll merge once that's done.

[laanwj]

Yep, good catch :) uploaded 0.10 final + signed SHA256SUMS.asc are in place.

Edit: Is the .dmg filename as expected?

Edit2: Indeed, SPV mode has not yet been implemented in 0.10 (there isn't even a pull for that as of now in master)

[saivann]

Note: I just updated the automatic torrent; all public trackers used appeared to be down so I added two others...

[harding]

@saivann cool. I'll redownload and update the magnet link if it changes.

[harding]

Merged. I also verified the .asc, checked it against some of the download from the site (I'll do the rest now) and against the all the files in the .torrent. Thanks!

[saivann]

Site has updated, looks all good!

The .dmg link works. I also confirm that signatures, torrent and magnet link are correct.

Thanks @harding and @laanwj, this is an historical release.

[schildbach]

Just an hour old, and it's already historical (-:

Thanks everyone!

[laanwj]

Confirmed it works. Thanks a lot @saivann and @harding!