Skip to content
This repository website

branch: master

Merge pull request #377 from bitcoin/releasesnotes

Add complete release notes
latest commit 71152dc55b
saivann saivann authored
Octocat-spinner-32 _alerts Update "Last updated" notice on Heartbleed alert page April 11, 2014
Octocat-spinner-32 _contrib Fix one regex in updatetx.rb April 07, 2014
Octocat-spinner-32 _events Add Event, Bitcoin Finance 2014 in Dublin, Ireland April 10, 2014
Octocat-spinner-32 _layouts Replace unused release announcement field by releases notes content April 12, 2014
Octocat-spinner-32 _less Prevent image from overflowing outside the container April 07, 2014
Octocat-spinner-32 _plugins Add temporary workaround for broken /heartbleed/ link April 11, 2014
Octocat-spinner-32 _releases Merge pull request #377 from bitcoin/releasesnotes April 16, 2014
Octocat-spinner-32 _templates Merge pull request #360 from greenaddress/master April 11, 2014
Octocat-spinner-32 _translations Merge pull request #360 from greenaddress/master April 11, 2014
Octocat-spinner-32 css Display events on a map using OpenStreetMap February 09, 2014
Octocat-spinner-32 en Rename "Bitcoin-Qt" to "Bitcoin Core" March 19, 2014
Octocat-spinner-32 font Add Persian (fa) translation (thanks Mohammad Rafigh, Foroozan Akhava… June 01, 2013
Octocat-spinner-32 img Added GreenAddress wallet April 09, 2014
Octocat-spinner-32 js Add Hungarian (hu) language March 05, 2014
Octocat-spinner-32 .gitignore add common useless OS files in .gitignore March 23, 2013
Octocat-spinner-32 404.html Switch to transifex for translations May 21, 2013
Octocat-spinner-32 COPYING Move Foundation logo to a separate folder March 18, 2014
Octocat-spinner-32 Replace unused release announcement field by releases notes content April 12, 2014
Octocat-spinner-32 _config.yml Update Chinese Translation April 10, 2014
Octocat-spinner-32 andreas_schildbach.asc Add gpg key for Andreas Schildbach (8B877A60). March 03, 2013
Octocat-spinner-32 bitcoin.pdf initial commit August 31, 2011
Octocat-spinner-32 bitcoin_es_latam.pdf First version of the Bitcoin paper translated to Spanish (Latin Ameri… January 30, 2014
Octocat-spinner-32 favicon.ico new March 18, 2013
Octocat-spinner-32 favicon.png temporary link to bitcoin-qt instead of multibit and a few minor fixes March 21, 2013
Octocat-spinner-32 gavinandresen.asc Update my pgp key December 09, 2013
Octocat-spinner-32 gmaxwell.asc Update my gpg key. July 14, 2013
Octocat-spinner-32 google40ba4724029a01dd.html Add new Google Webmaster Tools verification file February 01, 2014
Octocat-spinner-32 index.html Hide YouTube info bar January 26, 2014
Octocat-spinner-32 jgarzik-bitpay.asc Change Jeff Garzik public key and email address to bitpay May 23, 2013
Octocat-spinner-32 jgarzik-exmulti.asc initial commit August 31, 2011
Octocat-spinner-32 laanwj.asc add Wladimir to list of developers October 19, 2011
Octocat-spinner-32 pieterwuille.asc Updated my gpg key March 16, 2012
Octocat-spinner-32 robots.txt Use https urls in sitemap file January 31, 2014
Octocat-spinner-32 satoshinakamoto.asc Add Satoshi PGP key (fixes #79) April 06, 2013
Octocat-spinner-32 schneider.asc add press-list, renamed all PGP keys to .asc September 03, 2011

How to participate

You can report any problem or help to improve by opening an issue or a pull request on GitHub. You can also help translating on Transifex.

Working with GitHub

GitHub allows you to make changes to a project using git, and later submit them in a "pull request" so they can be reviewed and discussed. Many online how-tos exist so you can learn git, here's a good one.

In order to use GitHub, you need to sign up and set up git. You will also need to click the Fork button on the GitHub page and clone your GitHub repository into a local directory using the following command lines:

git clone (url provided by GitHub on your fork's page)
git remote add upstream

How to send a pull request

  1. Checkout to your master branch. git checkout master
  2. Create a new branch from the master branch. git checkout -b (any name)
  3. Edit files and preview the result.
  4. Track changes in files. git add -A
  5. Commit your changes. git commit -m '(short description for your change)'
  6. Push your branch on your GitHub repository. git push origin (name of your branch)
  7. Click on your branch on GitHub and click the Compare / pull request button to send a pull request.

When submitting a pull request, please take required time to discuss your changes and adapt your work. It is generally a good practice to split unrelated changes into separate branchs and pull requests.

How to make additional changes in a pull request

You simply need to push additionnal commits on the appropriate branch of your GitHub repository. That's basically the same steps as above, except you don't need to re-create the branch and the pull request.

How to reset and update your master branch with latest upstream changes

  1. Fetch upstream changes. git fetch upstream
  2. Checkout to your master branch. git checkout master
  3. Replace your master branch by the upstream master branch. git reset --hard upstream/master
  4. Replace your master branch on GitHub. git push origin master -f


Easy preview: Simple text changes can be previewed live on You only need to click anywhere on the page and hold your mouse button for one second. You'll then be able to edit the page just like a document. Changes will be lost as soon as the page is refreshed.

Real preview: Install dependencies, run jekyll (or "jekyll build" on older setups), and copy the output files from _site/ to the root of your web server. If you have no web server, run jekyll --server (or "jekyll serve" on older setups). This server requires you to add a trailing ".html" by hand in your browser address bar.


Installing dependencies on Ubuntu 12.10

sudo apt-get install jekyll node-less ruby1.9.1-dev libicu-dev
sudo gem install ffi-icu

Installing dependencies on older Ubuntu and Debian distributions

sudo apt-get install rubygems ruby1.9.1-dev build-essential libicu-dev
sudo gem install jekyll json less therubyracer ffi-icu


How to translate

You can join a translation team on Transifex and start translating or improving existing translations. Latest live previews and communications can be found on this thread.

  • You must be a native speaker for the language you choose to translate.
  • Please be careful to preserve the original meaning of each text.
  • Sentences and popular expressions should sound native in your language.
  • Translations need to be reviewed by a reviewer or coordinator before publication.
  • Once reviewed, translations can be submitted in a pull request on GitHub.
  • In doubt, please open a discussion on Transifex with coordinators. That'll be much appreciated.

Import translations

Update translations: You can update the relevant language file in _translations/ and from the root of the git repository run ./_contrib/updatetx.rb to update layouts and templates for this language. You should also make sure that no url has been changed by translators. If any page needs to be moved, please add redirections.

Add a new language: You can put the language file from Transifex in _translations and add the language in _config.yml in the right display order for the language bar. Make sure to review all pages and check all links.

Update english strings

Any change in the english texts can be done through a pull request on GitHub. If your changes affect the html layout of a page, you should apply fallback html code for other languages until they are updated.

{% case page.lang %}
{% when 'fr' %}
  (outdated french content)
{% else %}
  (up to date english content)
{% endcase %}

When translation is needed: If you want all changes you've made to be re-translated, you can simply update the resource file (en.yml) on Transifex.

When translation is not needed: If you are only pushing typo fixes and that you don't want translators to redo all their work again, you can use the Transifex client to pull translations, update en.yml and push back all translations at once:

tx init
tx set --auto-remote
tx pull -a -s --skip
tx set --source -r bitcoinorg.bitcoinorg -l en translations/bitcoinorg.bitcoinorg/en.yml
(update en.yml)
tx push -s -t -f --skip --no-interactive



Events should be placed in _events/ and adhere to this format:

date: 2014-02-21
title: "2014 Texas Bitcoin Conference"
venue: "Circuit of the Americas™ - Technology and Conference Center"
address: "9201 Circuit of the Americas Blvd"
city: "Austin, TX"
country: "United States"
link: ""

Release Notes

Release notes should be placed in _releases/ and adhere to this format:

title: Bitcoin Core version 0.9.0 released

Bitcoin Core v0.9.0 is now available for download at

  • VERSION is used to define the version and construct the URL. It should adhere to this format: v0.3.24.
  • title: ... will be used as the title


Network alerts should be placed in _alerts/YYYY-MM-DD-SHORTITLE.html and adhere to this format:

title: "11/12 March 2013 Chain Fork"
alias: "chainfork"
active: true
banner: "<b>Chain fork</b> - Please stop mining on bitcoin version 0.8.0. Click here for more information."

A chain fork is happening. Please stop mining on bitcoin version 0.8.0. Your bitcoins are safe but it is recommended that you postpone your Bitcoin transactions for the next hours.
More information will follow.
<div style="text-align:right">
  <i>This notice last updated: Thu, 16 May 2013 01:37:00 UTC</i>

  • SHORTTITLE is used to construct the URL.
  • title: ... will be used as the title in the layout.
  • alias: ... (optional) a short alias for Bitcoin Core alerts. Ex. "dos" will produce /dos.html
  • active: ... (true or false) define if the alert should appear as ongoing in the network status page.
  • banner: ... (optional) a short text that will be displayed in a red alert banner and link to the alert page.
  • last updated: ... should be kept up to date and be in RFC 2822 format ( date -uR ).

Advanced Usage


Redirections can be defined in _config.yml.

  /news: /en/version-history

Aliases for contributors

Aliases for contributors are defined in _config.yml.

  s_nakamoto: Satoshi Nakamoto
  --author=Satoshi Nakamoto: Satoshi Nakamoto
  gavinandresen: Gavin Andresen
Something went wrong with that request. Please try again.