-
-
Notifications
You must be signed in to change notification settings - Fork 41
Update 3.2 release blog post in prep for tomorrow’s release. #63
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
Conversation
|
||
RSpec continues to be a community-driven project with contributors | ||
from all over the world. This release includes 647 commits from 190 | ||
pull requests from 47 different contributors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, really?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the numbers are even higher (see stats below). This is copied in from the 3.1 release post. I plan to update it and/or rewrite this section.
I skimmed this, looks good though |
|
||
### Core: Pending Example Output Includes Failure Details | ||
|
||
RSpec 3.0 shipped with new semantics for `pending`: rather than |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace ':' with a period? Seems like a sentence break instead of a definition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
OK, I updated it some more. This is what I plan to publish tomorrow (sans replacing some bits that are generated by rspec-dev rake tasks). |
Update 3.2 release blog post in prep for tomorrow’s release.
This is most of the blog post that I'll be publishing tomorrow after releasing 3.2. There are still a few TODOs but I'm done with it for the night -- the rest I'll wrap up tomorrow.
I don't want to hold back the release of 3.2 or the publishing of this post based on waiting for a review so I plan to merge and deploy this tomorrow regardless of if anyone reviews it or not...but if any one wants to, feel free and I'll revise based on feedback.