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
186 lines
5.5 KiB
Markdown
186 lines
5.5 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.6.0
|
|
optional_date: 2012-03-30
|
|
title: Bitcoin-Qt version 0.6.0 released
|
|
---
|
|
Bitcoin-Qt version 0.6.0 is now available for download at:
|
|
<http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/>
|
|
|
|
This release includes more than 20 language localizations.
|
|
More translations are welcome; join the
|
|
project at Transifex to help:
|
|
<https://www.transifex.net/projects/p/bitcoin/>
|
|
|
|
Please report bugs using the issue tracker at github:
|
|
<https://github.com/bitcoin/bitcoin/issues>
|
|
|
|
Project source code is hosted at github; we are no longer
|
|
distributing .tar.gz files here, you can get them
|
|
directly from github:
|
|
<https://github.com/bitcoin/bitcoin/tarball/v0.6.0> # .tar.gz
|
|
<https://github.com/bitcoin/bitcoin/zipball/v0.6.0> # .zip
|
|
|
|
For Ubuntu users, there is a ppa maintained by Matt Corallo which
|
|
you can add to your system so that it will automatically keep
|
|
bitcoin up-to-date. Just type
|
|
sudo apt-add-repository ppa:bitcoin/bitcoin
|
|
in your terminal, then install the bitcoin-qt package.
|
|
|
|
|
|
KNOWN ISSUES
|
|
------------
|
|
|
|
Shutting down while synchronizing with the network
|
|
(downloading the blockchain) can take more than a minute,
|
|
because database writes are queued to speed up download
|
|
time.
|
|
|
|
|
|
NEW FEATURES SINCE BITCOIN VERSION 0.5
|
|
--------------------------------------
|
|
|
|
Initial network synchronization should be much faster
|
|
(one or two hours on a typical machine instead of ten or more
|
|
hours).
|
|
|
|
Backup Wallet menu option.
|
|
|
|
Bitcoin-Qt can display and save QR codes for sending
|
|
and receiving addresses.
|
|
|
|
New context menu on addresses to copy/edit/delete them.
|
|
|
|
New Sign Message dialog that allows you to prove that you
|
|
own a bitcoin address by creating a digital
|
|
signature.
|
|
|
|
New wallets created with this version will
|
|
use 33-byte 'compressed' public keys instead of
|
|
65-byte public keys, resulting in smaller
|
|
transactions and less traffic on the bitcoin
|
|
network. The shorter keys are already supported
|
|
by the network but wallet.dat files containing
|
|
short keys are not compatible with earlier
|
|
versions of Bitcoin-Qt/bitcoind.
|
|
|
|
New command-line argument `-blocknotify=<command>`
|
|
that will spawn a shell process to run `<command>`
|
|
when a new block is accepted.
|
|
|
|
New command-line argument -splash=0 to disable
|
|
Bitcoin-Qt's initial splash screen
|
|
|
|
validateaddress JSON-RPC api command output includes
|
|
two new fields for addresses in the wallet:
|
|
pubkey : hexadecimal public key
|
|
iscompressed : true if pubkey is a short 33-byte key
|
|
|
|
New JSON-RPC api commands for dumping/importing
|
|
private keys from the wallet (dumprivkey, importprivkey).
|
|
|
|
New JSON-RPC api command for getting information about
|
|
blocks (getblock, getblockhash).
|
|
|
|
New JSON-RPC api command (getmininginfo) for getting
|
|
extra information related to mining. The getinfo
|
|
JSON-RPC command no longer includes mining-related
|
|
information (generate/genproclimit/hashespersec).
|
|
|
|
|
|
|
|
NOTABLE CHANGES
|
|
---------------
|
|
|
|
BIP30 implemented (security fix for an attack involving
|
|
duplicate "coinbase transactions").
|
|
|
|
The -nolisten, -noupnp and -nodnsseed command-line
|
|
options were renamed to -listen, -upnp and -dnsseed,
|
|
with a default value of 1. The old names are still
|
|
supported for compatibility (so specifying -nolisten
|
|
is automatically interpreted as -listen=0; every
|
|
boolean argument can now be specified as either
|
|
-foo or -nofoo).
|
|
|
|
The -noirc command-line options was renamed to
|
|
-irc, with a default value of 0. Run -irc=1 to
|
|
get the old behavior.
|
|
|
|
Three fill-up-available-memory denial-of-service
|
|
attacks were fixed.
|
|
|
|
NOT YET IMPLEMENTED FEATURES
|
|
----------------------------
|
|
|
|
Support for clicking on bitcoin: URIs and
|
|
opening/launching Bitcoin-Qt is available only on Linux,
|
|
and only if you configure your desktop to launch
|
|
Bitcoin-Qt. All platforms support dragging and dropping
|
|
bitcoin: URIs onto the Bitcoin-Qt window to start
|
|
payment.
|
|
|
|
|
|
PRELIMINARY SUPPORT FOR MULTISIGNATURE TRANSACTIONS
|
|
---------------------------------------------------
|
|
|
|
This release has preliminary support for multisignature
|
|
transactions-- transactions that require authorization
|
|
from more than one person or device before they
|
|
will be accepted by the bitcoin network.
|
|
|
|
Prior to this release, multisignature transactions
|
|
were considered 'non-standard' and were ignored;
|
|
with this release multisignature transactions are
|
|
considered standard and will start to be relayed
|
|
and accepted into blocks.
|
|
|
|
It is expected that future releases of Bitcoin-Qt
|
|
will support the creation of multisignature transactions,
|
|
once enough of the network has upgraded so relaying
|
|
and validating them is robust.
|
|
|
|
For this release, creation and testing of multisignature
|
|
transactions is limited to the bitcoin test network using
|
|
the "addmultisigaddress" JSON-RPC api call.
|
|
|
|
Short multisignature address support is included in this
|
|
release, as specified in BIP 13 and BIP 16.
|
|
|
|
|
|
Thanks to everybody who contributed to this release:
|
|
|
|
- Alex B
|
|
- Alistair Buxton
|
|
- Chris Moore
|
|
- Clark Gaebel
|
|
- Daniel Folkinshteyn
|
|
- Dylan Noblesmith
|
|
- Forrest Voight
|
|
- Gavin Andresen
|
|
- Gregory Maxwell
|
|
- Janne Pulkkinen
|
|
- Joel Kaartinen
|
|
- Lars Rasmusson
|
|
- Luke Dashjr
|
|
- Matt Corallo
|
|
- Michael Ford
|
|
- Michael Hendricks
|
|
- Nick Bosma
|
|
- Nils Schneider
|
|
- Philip Kaufmann
|
|
- Pierre Pronchery
|
|
- Pieter Wuille
|
|
- Rune K Svendsen
|
|
- Wladimir J. van der Laan
|
|
- coderrr
|
|
- p2k
|
|
- sje397
|
|
|
|
Special thanks to Sergio Lerner and Matt Corallo for bringing
|
|
potential denial-of-service attacks to our attention.
|