Prepare for a 1.3.0.rc release #1667

merged 2 commits into from Oct 30, 2013


None yet

5 participants

mattr- commented Oct 29, 2013

I'd like to do a 1.3.0.rc release before releasing finally releasing 1.3.0. Hopefully we'll get enough feedback that we can shake out any issues before we do a 1.3.0 final release (which I'm thinking right now would be at the end of the week)

parkr commented Oct 29, 2013

Added the release post to the gem spec.

LGTM! Merge when you're ready :)

shigeya commented Oct 29, 2013


@mattr- mattr- merged commit eff0214 into master Oct 30, 2013

1 check passed

default The Travis CI build passed
@mattr- mattr- deleted the release-1.3.0.rc branch Oct 30, 2013

Next time around, may make sense to link out to the change log, the tag, how to test, etc.

As an outsider, almost reads as Hey, we made a bunch of changes (we're not telling you what though), and you should go test them (but we're not going to say how).


Good points all around. I will definitely do better for next time.


Why not add that now?


Tired, sick, and still recovering. Once I feel closer to 100% I'll polish things up for a 1.3.0 release


Next time around, may make sense to link out to the change log, the tag, how to test, etc.

Absolutely. I wanted to try out the new data feature at this weekend, but I don’t even know how to install the RC. Jekyll is the only Ruby software I use. I don’t have time to learn the whole Ruby universe just to try out the new RC.

parkr commented Nov 1, 2013

@penibelst, the only difference between a normal install and an RC install is a --pre switch when running gem install.

You can do either of these 2 things:

$ gem install jekyll --pre
# or
$ gem install jekyll -v 1.3.0.rc

@parkr Thanks, I get the RC.

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