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 Jekyll 2.0.0 release post. #2298

Merged
merged 11 commits into from May 6, 2014

Conversation

Projects
None yet
7 participants
@parkr
Member

parkr commented May 5, 2014

/cc @benbalter – would love your πŸ‘€ before we release.

  • Sell the new features, don't just list them
  • List contributors
  • Be even more nostalgic about the release date

screen shot 2014-05-05 at 3 05 59 am
#2166

@parkr parkr added this to the 2.0 milestone May 5, 2014

3. [Native Sass & CoffeeScript support](/docs/assets/)
4. [YAML Front-Matter defaults](/docs/configuration/#frontmatter_defaults)
5. Custom markdown processors
6. Addition of `where` and `sort_by` Liquid filters

This comment has been minimized.

@doktorbro

doktorbro May 5, 2014

Member

It was group_by, not sort_by.

@doktorbro

This comment has been minimized.

Member

doktorbro commented May 5, 2014

Please list some breaking changes.

@@ -0,0 +1,28 @@
---
layout: news_item
title: 'Jekyll 2.0.0 Released'

This comment has been minimized.

@benbalter

benbalter May 5, 2014

Contributor

Jekyll's not boring, so why should our blog titles be? Perhaps "Jekyll turns 2.0.0" or "We're proud to announce the birth of Jekyll 2.0.0" or something slightly more human?

---
layout: news_item
title: 'Jekyll 2.0.0 Released'
date: 2014-05-05 02:50:09 -0400

This comment has been minimized.

@benbalter

benbalter May 5, 2014

Contributor

More curiousity, if time isn't displayed, why not just use the filename date?

This comment has been minimized.

@parkr

parkr May 5, 2014

Member

It's auto-generated in the rake task. No definite reason to use it.

categories: [release]
---
One year ago, [we released Jekyll 1.0.0][jekyll-1]. One year later, we present to you the next major version: Jekyll 2.0.

This comment has been minimized.

@benbalter

benbalter May 5, 2014

Contributor

2013-05-06... depending on timing, may be cool to note "almost a year later to the day...."

One year ago, [we released Jekyll 1.0.0][jekyll-1]. One year later, we present to you the next major version: Jekyll 2.0.
Jam-packed with some [highly-requested features and bugfixes galore][changelog], this is the best Jekyll yet. Some notable changes:

This comment has been minimized.

@benbalter

benbalter May 5, 2014

Contributor

Reads a lot like you're giving me a drill, but not the 1/4" hole that I really want. For each of these, I'd put them in the format of THING WITH LINK - Why I should care. E.g.,:

  • Collections - Collections allow you to define an unlimited number of custom document types (beyond just posts and pages) for different types of content you may want to author in Jekyll such as software documentation or ____.
  • YAML Front-Matter defaults - Do all your posts use your post layout? Front-matter defaults allow you to set it once and forget it!
    etc...
@benbalter

This comment has been minimized.

Contributor

benbalter commented May 5, 2014

Forgot where we landed, but if so, may want to include the contributors' list.

@parkr

This comment has been minimized.

Member

parkr commented May 5, 2014

Forgot where we landed, but if so, may want to include the contributors' list.

Would love to. According to the docs, though, we can't filter by compare, so we just get everyone.

@mattr-

This comment has been minimized.

Member

mattr- commented May 5, 2014

git shortlog -sn v1.0.0...v2.0.0.rc1 | cut -d ' ' -f2- should give you the list of all the people between the two tags. that whitespace character is Tab which you can enter by using Ctrl+V and then hitting Tab. No, we can't link to their GitHub profile, but that's ok, IMHO

@parkr

This comment has been minimized.

Member

parkr commented May 5, 2014

Awesome!! Thanks, @mattr-!! I've saved this for later use: https://github.com/parkr/dotfiles/blob/master/bin/git-contributors

@parkr

This comment has been minimized.

Member

parkr commented May 6, 2014

Alrighty, lots of updates to this. @benbalter, would you mind giving it another pass?

categories: [release]
---
Almost a year later to the day, [we released Jekyll 1.0.0][jekyll-1]. One year later, we present to you the next major version: Jekyll 2.0.

This comment has been minimized.

@benbalter

benbalter May 6, 2014

Contributor

Almost a year later to the day, [we released Jekyll 1.0.0][jekyll-1].

s/later/ago

This comment has been minimized.

@benbalter

benbalter May 6, 2014

Contributor

Jekyll 2.0.

Jekyll 2.0.0?

@benbalter

This comment has been minimized.

Contributor

benbalter commented May 6, 2014

πŸ’– when's the big day?

@madhur

This comment has been minimized.

madhur commented May 6, 2014

Great feeling as we near 2.0.0 release. I will also make sure to update the portable Jekyll package as soon as 2.0.0 is out πŸ˜„
http://www.madhur.co.in/blog/2013/07/20/buildportablejekyll.html

@jordanthornquest

This comment has been minimized.

Contributor

jordanthornquest commented May 6, 2014

Ahh! Are we ready to go?

@mattr-

This comment has been minimized.

Member

mattr- commented May 6, 2014

:shipit:

giphy

parkr added a commit that referenced this pull request May 6, 2014

@parkr parkr merged commit d2c5668 into master May 6, 2014

1 check passed

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

@parkr parkr deleted the release-post branch May 6, 2014

parkr added a commit that referenced this pull request May 6, 2014

@parkr parkr referenced this pull request May 6, 2014

Closed

Release 2.0 #2166

[changelog]: /docs/history/
[@jglovier]: https://github.com/jglovier
[jekyll-1]: {% post_url 2013-05-05-jekyll-1-0-0-released %}

This comment has been minimized.

@doktorbro

doktorbro May 6, 2014

Member

Must be {% post_url 2013-05-06-jekyll-1-0-0-released %}.

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

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