New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release blog post for 0.13.1 #241

Merged
merged 3 commits into from Oct 27, 2016

Conversation

Projects
None yet
4 participants
@harding
Contributor

harding commented Oct 27, 2016

This adds a release blog post for 0.13.1.

TODO

  • This assumes the release date is Monday 31 Oct 2016. If it as any other date, the file needs to be moved and the YAML header needs to edited.
  • At the very top of the document, a link needs to be added to @laanwj's PGP-signed release announcement (as we did with the previous release). The tests should fail until this is added, but I see they succeeded, which I guess means I'll have to fix that...
  • The SHA256 hashes of the release files should be added to the bottom of this document (the "Hashes for verification" section) as was done for the previous release.
  • #240 needs to be merged before this, or this document needs to be edited to stop linking to it. (The tests should also be failing because that's missing in this branch...)

A preview for the blog post as of fd37386 may be found at: http://imgur.com/a/gKi9W

The post entry on the main page looks like this:

2016-10-26-21_01_20_253721417

Please note that if you attempt to generate a preview of this document, you will need to add --future to Jekyll's parameters because the post is dated for 2016-10-31.

Several people provided suggestions on this in draft form, for which I am very grateful. Any errors that appear in this version are entirely my fault. For anyone who read the final draft version, I've made a few small changes:

  1. I further shortened some of the descriptions in the new features summary section at the top. The only significant phrasing change is in point 7 (More efficient almost-full-node security). I added a few paragraph breaks in the corresponding detail subsections but no words were changed there.
  2. To the end of the document, I added a new Conclusion section (and also the template Hashes For Verification section) to match the format of the 0.13.0 release blog.
  3. I changed the opening to the null dummy section to make it flow a little better.

As requested in some of the draft feedback, I added the ability to link directly to each of the items on the timeline. This is a little bit ugly, so I'm open to suggestions for making it look nicer. Screenshot below (the # are both the link and the anchor):

2016-10-26-21_07_22_112758683

@harding harding added the blog label Oct 27, 2016

@btcdrak

This comment has been minimized.

Show comment
Hide comment
@btcdrak

btcdrak Oct 27, 2016

Contributor

Can you also add a copy of the release notes?

Contributor

btcdrak commented Oct 27, 2016

Can you also add a copy of the release notes?

@Michagogo

This comment has been minimized.

Show comment
Hide comment
@Michagogo

Michagogo Oct 27, 2016

@btcdrak AIUI there's supposed to be a link to them at the top, once @laanwj pgp-signs and posts them.

Michagogo commented Oct 27, 2016

@btcdrak AIUI there's supposed to be a link to them at the top, once @laanwj pgp-signs and posts them.

@Michagogo

This comment has been minimized.

Show comment
Hide comment
@Michagogo

Michagogo Oct 27, 2016

Unless the release announcement is something else?

Michagogo commented Oct 27, 2016

Unless the release announcement is something else?

@Michagogo

This comment has been minimized.

Show comment
Hide comment
@Michagogo

Michagogo Oct 27, 2016

No, looks like it is indeed the ML post with the release notes.

Michagogo commented Oct 27, 2016

No, looks like it is indeed the ML post with the release notes.

@btcdrak

This comment has been minimized.

Show comment
Hide comment
@btcdrak

btcdrak Oct 27, 2016

Contributor

@Michagogo No, the release notes are not signed, you're thinking of the release announcement which has the signed hashes. The release notes are separate, check "releases" on the website.

Contributor

btcdrak commented Oct 27, 2016

@Michagogo No, the release notes are not signed, you're thinking of the release announcement which has the signed hashes. The release notes are separate, check "releases" on the website.

@Michagogo

This comment has been minimized.

Show comment
Hide comment
@Michagogo

Michagogo Oct 27, 2016

Ah, I see.

Michagogo commented Oct 27, 2016

Ah, I see.

@harding

This comment has been minimized.

Show comment
Hide comment
@harding

harding Oct 27, 2016

Contributor

Fixed feedback from @btcdrak and @kanzure (thanks!) and rebased on top of merge that includes the segwit upgrade guide (and checked the preview and cross-link to ensure they worked).

Contributor

harding commented Oct 27, 2016

Fixed feedback from @btcdrak and @kanzure (thanks!) and rebased on top of merge that includes the segwit upgrade guide (and checked the preview and cross-link to ensure they worked).

@harding

This comment has been minimized.

Show comment
Hide comment
@harding

harding Oct 27, 2016

Contributor

Also just added release notes. This is a copy of https://raw.githubusercontent.com/bitcoin/bitcoin/2e2388a5cbb9a6e101b36e4501698fec538a5738/doc/release-notes/release-notes-0.13.1.md with the following global substitution to fix a formatting difference between GitHub-flavor Markdown and the Markdown used on this site: s/^- #/- \\#/ (e.g. the list items that start with a # are rendered as subheadings on BitcoinCore.org; this prefaces them with a backslash to have them render normally as #)

Contributor

harding commented Oct 27, 2016

Also just added release notes. This is a copy of https://raw.githubusercontent.com/bitcoin/bitcoin/2e2388a5cbb9a6e101b36e4501698fec538a5738/doc/release-notes/release-notes-0.13.1.md with the following global substitution to fix a formatting difference between GitHub-flavor Markdown and the Markdown used on this site: s/^- #/- \\#/ (e.g. the list items that start with a # are rendered as subheadings on BitcoinCore.org; this prefaces them with a backslash to have them render normally as #)

@btcdrak

This comment has been minimized.

Show comment
Hide comment
@btcdrak

btcdrak Oct 27, 2016

Contributor

OK released, pulling the trigger now.

Contributor

btcdrak commented Oct 27, 2016

OK released, pulling the trigger now.

@btcdrak btcdrak merged commit b5a7aef into gh-pages Oct 27, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

btcdrak added a commit that referenced this pull request Oct 27, 2016

Merge #241: Add release blog post for 0.13.1
b5a7aef 0.13.1 release: add release notes (David A. Harding)
f1a286e 0.13.1 release blog: fix exerpt; update link (David A. Harding)
313dc18 Add release blog post for 0.13.1 (David A. Harding)

@btcdrak btcdrak deleted the release-0.13.1 branch Oct 27, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment