-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Release rspec-rails 3.8.2 #2066
Comments
For the moment we have master...3-8-maintenance So it means:
We have a good checklist but for minor versions. rspec/rspec-dev#204 I am wondering how much I could follow it for rspec-rails patch release. |
My own personal check list is:
|
Thanks a lot for the list. I will probably try do it tomorrow. What do you think about including #2047? I don't have |
The `rake release` rights are what Sam is organising for you, so hopefully by the time you’re ready you’ll have what you need :)
Jon Rowe
---------------------------
mail@jonrowe.co.uk
jonrowe.co.uk
…On 12 January 2019 at 22:14, Benoit Tigeot wrote:
Thanks a lot for the list.
I will probably try do it tomorrow. What do you think about including #2047 (#2047)?
I don't have rake release rights. Maybe the best for the first time is a PR from my fork to 3-8-mainteance so we can agree about which commits will be included into 3.8.2.
|
Checklist done in #2067 (comment) 🎉 Thanks a lot Sam and Jon |
Yesssss
On Fri, 18 Jan 2019 at 13:41, Benoit Tigeot ***@***.***> wrote:
Closed #2066 <#2066>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2066 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAF5lmD7IwogQ398fpI7oqn1E2KZ8PlXks5vEc8bgaJpZM4Z7YCL>
.
--
Sam Phippen
|
Given that there aren't any new features merged in to master, let's make sure we've forward-ported all the bugfixes and enhancements from
master
to3-8-maintenance
and release3.8.2
so that we can then begin the process of developing RSpec Rails 4.@benoittgt do you want to tackle this issue?
The text was updated successfully, but these errors were encountered: