mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +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
41 lines
1.6 KiB
HTML
41 lines
1.6 KiB
HTML
---
|
|
title: "February 20, 2012 Protocol Changes"
|
|
shorturl: "feb20"
|
|
active: false
|
|
banner: ""
|
|
date: 2012-02-18
|
|
---
|
|
<p>
|
|
In June 2010 the Bitcoin reference software version 0.2.10 introduced
|
|
a change to the protocol: the 'version' messages exchanged by nodes
|
|
at connection time would have a new format that included checksum
|
|
values to detect corruption by broken networks.
|
|
</p><p>
|
|
All other messages already carry a checksum (for connections between
|
|
nodes 0.2.9 and later) but the version messages themselves could not
|
|
be changed in a compatible way, so this change was delayed and did not take effect until
|
|
<a href="http://www.timeanddate.com/worldclock/fixedtime.html?msg=Bitcoin+protocol+change&iso=20120220T00">midnight UTC on Feb 20th 2012</a>
|
|
to leave users time to upgrade.
|
|
</p><p>
|
|
The developers of the Bitcoin reference software are unable to find
|
|
any evidence of any nodes still running software prior to 0.2.10 on
|
|
the network. If any nodes with software this old
|
|
do still exist, they will no longer be able to connect to newer nodes.
|
|
</p><p>
|
|
This switchover has been tested and no significant disruption is
|
|
expected and none has been observed so far.
|
|
Nodes with incorrect clocks may have a difficult
|
|
time making new connections for a brief period around the switchover
|
|
time.
|
|
</p><p>
|
|
Please report any new connectivity issues to the <a
|
|
href="http://webchat.freenode.net/?channels=bitcoin-dev&uio=d4">#bitcoin-dev
|
|
channel</a> on Freenode IRC.
|
|
</p><p>
|
|
If there are unexpected difficulties this page will be updated with
|
|
relevant information.
|
|
</p>
|
|
|
|
<div style="text-align:right">
|
|
<i>This notice last updated: Mon, 20 Feb 2012 00:10:00 UTC</i>
|
|
</div>
|