mirror of
https://github.com/seigler/dash-docs
synced 2025-07-28 10:16:15 +00:00
7d98f798ab
Gemfile:
- Upgrade to Jekyll 3.x (3.0.1 tested). This brings several new
features I want to use, most notably *collections* which allows us
to add blog-like collections. I've converted the `_releases` and
`_alerts` pages into collections, although their plugins are
maintained to handle the Download and Active Alert features.
- Upgrade to latest Kramdown.
- Lock Less at 2.4.0. This prevents breaking our Less plugin. Jekyll
3.x provides native support for SCSS, so we may want to switch to
that in time.
- Lock HTML Proofer at 2.1.0. The most recent version was taking
forever to check our pages (I never actually got it to complete).
I'll look into it when I get more time.
Makefile:
- New `make clean` command. Jekyll 3.x by default attempts to do
incremental rebuilds. The new `jekyll clean` command cleans up the
metadata necessary for than so that a full build is performed, and
this new `make clean` command is a wrapper around it so that we
automatically do full rebuilds in the relevant cases. Note: our
plugins aren't fully compatible with the incremental rebuilds, but
I'd like to fix that in the future.
- Remove WEBrick hack to enable previewing with default URL paths (/
instead of /index.html).
- Filter out compliants from Rouge
README.md:
- Now that Alerts (_alerts) are part of a collection, the file names
are no longer parsed for dates, so instructions on adding the date
to the YAML metadata have been added.
_alerts/*:
- Now that alerts are part of a collection, the file names are no
longer parsed to provide dates, so a `date:` field has been added to
the YAML metadata.
_config.yml:
- Some variables renamed per upgrade instructions.
- Switched from old default syntax highlighter Pygments to new default
Rouge. I tried to use Rouge options to keep new output as similar
to old output as possible to making diffing easy, but Rouge adds
extra CSS class info.
- Move `_alerts` and `_releases` into Jekyll 3.x "collections", which
provide the organizational features we were using plugins to
manange. I haven't removed the old plugins because we still use
some of their features (alerts.rb provides active issue and banner
features; releases.rb provides info to Download page)
- _layouts/* can no longer provide default global metadata; that is now
provided in the new `defaults:` section in _config.yml.
_layouts/*:
- Default metadata can no longer be provided in the layout files for
collections, so I've removed it and left a message to see
_config.yml.
_plugins/*:
- Remove filter_for.rb. It's completely broken on Jekyll 3.x because
of changes to Liquid which prevent adding new arguments to the
inherited Liquid::For class. Existing uses of filter_for have been
migrated to built-in for loops prefaced by sorts.
- Remove remove-html-extension.rb: at it said in the comments, this
was a temporary hack to get us to Jekyll 3.0.
_releases/*:
- Rename all the files: prefix a v to the file name so the output html
(e.g. v10.0.0.html) is the same as the source filename (e.g.
v10.0.0.md). This is necessary to migrate them to a Jekyll collection.
- Remove %v from titles: we have to explicitly set the title, like we
used to. Again required for migration to collections.
_templates/events.html & en/rss/events.rss:
- Sort events by date and then loop with regular for loop rather than
filter_for
en/alerts.html & en/rss/alerts.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
en/bitcoin-core/index.md & en/version-history.html & en/rss/releases.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
111 lines
3.9 KiB
Markdown
111 lines
3.9 KiB
Markdown
---
|
|
# This file is licensed under the MIT License (MIT) available on
|
|
# http://opensource.org/licenses/MIT.
|
|
# Text originally from Bitcoin Core project
|
|
# Metadata and small formatting changes from Bitcoin.org project
|
|
|
|
## Please see _releases/0.10.0.md for a release template
|
|
required_version: 0.5.0
|
|
optional_date: 2011-11-21
|
|
title: Bitcoin-Qt version 0.5.0 released
|
|
---
|
|
Bitcoin-Qt version 0.5.0 is now available for download at:
|
|
<http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/>
|
|
|
|
The major change for this release is a completely new graphical
|
|
that uses the Qt user interface toolkit.
|
|
|
|
This release includes German, Spanish, Spanish-Castilian, Norwegian
|
|
and Dutch translations. More translations are welcome; join the
|
|
project at Transifex if you can help:
|
|
<https://www.transifex.com/projects/p/bitcoin/>
|
|
|
|
Please report bugs using the issue tracker at GitHub:
|
|
<https://github.com/bitcoin/bitcoin/issues>
|
|
|
|
|
|
MAJOR BUG FIX (CVE-2011-4447)
|
|
------------------------------
|
|
|
|
The wallet encryption feature introduced in Bitcoin version 0.4.0
|
|
did not sufficiently secure the private keys. An attacker who
|
|
managed to get a copy of your encrypted wallet.dat file might be
|
|
able to recover some or all of the unencrypted keys and steal the
|
|
associated coins.
|
|
|
|
If you have a previously encrypted wallet.dat, the first time you
|
|
run bitcoin-qt or bitcoind the wallet will be rewritten, Bitcoin will
|
|
shut down, and you will be prompted to restart it to run with the new,
|
|
properly encrypted file.
|
|
|
|
If you had a previously encrypted wallet.dat that might have been
|
|
copied or stolen (for example, you backed it up to a public
|
|
location) you should send all of your bitcoins to yourself
|
|
using a new bitcoin address and stop using any previously
|
|
generated addresses.
|
|
|
|
Wallets encrypted with this version of Bitcoin are written properly.
|
|
|
|
Technical note: the encrypted wallet's 'keypool' will be regenerated the
|
|
first time you request a new bitcoin address; to be certain that the
|
|
new private keys are properly backed up you should:
|
|
|
|
1. Run Bitcoin and let it rewrite the `wallet.dat` file
|
|
|
|
2. Run it again, then ask it for a new bitcoin address.
|
|
|
|
Bitcoin-Qt: Address Book, then New Address...
|
|
|
|
bitcoind: run the `walletpassphrase` RPC command to unlock the wallet,
|
|
then run the `getnewaddress` RPC command.
|
|
|
|
3. If your encrypted wallet.dat may have been copied or stolen, send
|
|
all of your bitcoins to the new bitcoin address.
|
|
|
|
4. Shut down Bitcoin, then backup the wallet.dat file.
|
|
IMPORTANT: be sure to request a new bitcoin address before
|
|
backing up, so that the 'keypool' is regenerated and backed up.
|
|
|
|
"Security in depth" is always a good idea, so choosing a secure
|
|
location for the backup and/or encrypting the backup before
|
|
uploading it is recommended. And as in previous releases, if your
|
|
machine is infected by malware there are several ways an
|
|
attacker might steal your bitcoins.
|
|
|
|
Thanks to Alan Reiner (aka etotheipi) for finding and reporting
|
|
this bug.
|
|
|
|
MAJOR GUI CHANGES
|
|
-----------------
|
|
|
|
* "Splash" graphics at startup that show address/wallet/blockchain loading
|
|
progress.
|
|
|
|
* "Synchronizing with network" progress bar to show block-chain download
|
|
progress.
|
|
|
|
* Icons at the bottom of the window that show how well connected you are
|
|
to the network, with tooltips to display details.
|
|
|
|
* Drag and drop support for bitcoin: URIs on web pages.
|
|
|
|
* Export transactions as a .csv file.
|
|
|
|
* Many other GUI improvements, large and small.
|
|
|
|
RPC CHANGES
|
|
-----------
|
|
|
|
* getmemorypool : new RPC command, provides everything needed to construct
|
|
a block with a custom generation transaction and submit a solution
|
|
|
|
* listsinceblock : new RPC command, list transactions since given block
|
|
|
|
* signmessage/verifymessage : new RPC commands to sign a message with
|
|
one of your private keys or verify that a message signed by the private
|
|
key associated with a bitcoin address.
|
|
|
|
GENERAL CHANGES
|
|
---------------
|
|
|
|
* Faster initial block download.
|