Prepare for 2.1.0 release #110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gsamokovarov
force-pushed
the
prepare-for-2-1-release
branch
3 times, most recently
from
08b0d3f
to
6fd5d56
Compare
gsamokovarov
force-pushed
the
prepare-for-2-1-release
branch
3 times, most recently
from
02b0d54
to
8584311
Compare
With Rails 4.2.1 coming soon, I think we can catch its release train and roll out 2.1.0. I have tweaked the README to reflect the recent changes and will put in shape the CHANGELOG. I also did a bit of cleanup that was on my list, the biggest one being, that we are no longer an engine, but a railtie as we don't use any of the engine features anymore. Another one is exposing `config.web_console.acceptable_content_types`, but only for potential user support, if we hit another Puma-like issue. I don't intend to document it in the README.
gsamokovarov
added a commit
that referenced
this pull request
Feb 28, 2015
Prepare for 2.1.0 release
gsamokovarov
added a commit
to gsamokovarov/rails
that referenced
this pull request
Mar 2, 2015
With the upcoming 2.1 [web-console release], I have tweaked the existing documentation a bit. I tried to focus on the spawning console use case, because I think a lot of people overlook that. Tried to explain it as best as I can, however, my English and prose aren't my best skills :) If you guys can chime in and help me improve the wording, I would be extremely grateful. There has been some configuration default changes. For example, the whitelisted IPs always include IPv4 and IPv6 localhosts now and this wasn't the case in 2.0. I think a lot of people got bitten by it, that's why I changed it. I'm a bit confused on how to document this. Should I just document the latest version, I don't think I can expect all the people reading the guide to be on it. [web-console release]: rails/web-console#110
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With Rails 4.2.1 coming soon, I think we can catch its release train and
roll out 2.1.0.
I have tweaked the README to reflect the recent changes and be a bit.more concise and will put in shape the changelog shortly
Will also updatethe
web-consolebit in the debugging guide on Rails upstream side.I have one issue left for review: #109.@rafaelfranca, @chancancode, @guilleiguaran ping me if you need
something else for the release.