[Rails-core] [ANN] Rails 3.2.9 has been released!!!
Hi everyone, Rails 3.2.9 has been released without new changes since 3.2.9.rc3. ## IMPORTANT! A DoS attack was recently found in Ruby that uses specially-crafted input to dramatically reduce the performance of hashes, thus using up lots of CPU time. Rails applications may be vulnerable to an attacker sending a specially-crafted HTTP request to exploit this. A good way to limit the effectiveness of such attacks is to configure your frontend servers to limit the size of the HTTP request line, headers and body. Nginx does this by default. Apache can be configured to do this by setting the LimitRequestBody directive. In addition, all Ruby 1.9 users are recommended to upgrade to [ruby-1.9.3 patchlevel 327](http://www.ruby-lang.org/en/news/2012/11/09/ruby-1-9-3-p327-is-released/) to get this security fix. ## CHANGES since 3.2.8 *Action Mailer* * Do not render views when mail() isn't called. Fix #7761 *Yves Senn* *Action Pack* * Lock sprockets to 2.2.x REASON: We had some pending fixes in sprockets and sass-rails to make possible to use sprockets version 2.2. We will do a more conservative sprockets upgrade for this release. In a next release we can relax the dependency again. See #8099 for more information. *Guillermo Iguaran* * Clear url helpers when reloading routes. *Santiago Pastorino* * Revert the shorthand routes scoped with `:module` option fix This added a regression since it is changing the URL mapping. This makes the stable release backward compatible. *Rafael Mendonça França* * Revert the `assert_template` fix to not pass with ever string that matches the template name. This added a regression since people were relying on this buggy behavior. This will introduce back #3849 but this stable release will be backward compatible. Fixes #8068. *Rafael Mendonça França* * Revert the rename of internal variable on ActionController::TemplateAssertions to prevent naming collisions. This added a regression related with shoulda-matchers, since it is expecting the [instance variable @layouts](https://github.com/thoughtbot/shoulda-matchers/blob/9e1188eea68c47d9a56ce6280e45027da6187ab1/lib/shoulda/matchers/action_controller/render_with_layout_matcher.rb#L74). This will introduce back #7459 but this stable release will be backward compatible. Fixes #8068. *Rafael Mendonça França* * Accept :remote as symbolic option for `link_to` helper. *Riley Lynch* * Warn when the `:locals` option is passed to `assert_template` outside of a view test case Fix #3415 *Yves Senn* * Rename internal variables on ActionController::TemplateAssertions to prevent naming collisions. @partials, @templates and @layouts are now prefixed with an underscore. Fix #7459 *Yves Senn* * `resource` and `resources` don't modify the passed options hash Fix # *Yves Senn* * Precompiled assets include aliases from foo.js to foo/index.js and vice versa. # Precompiles phone-digest.css and aliases phone/index.css to phone.css. config.assets.precompile = [ 'phone.css' ] # Precompiles phone/index-digest.css and aliases phone.css to phone/index.css. config.assets.precompile = [ 'phone/index.css' ] # Both of these work with either precompile thanks to their aliases. %= stylesheet_link_tag 'phone', media: 'all' % %= stylesheet_link_tag 'phone/index', media: 'all' % *Jeremy Kemper* * `assert_template` is no more passing with what ever string that matches with the template name. Before when we have a template `/layout/hello.html.erb`, `assert_template` was passing with any string that matches. This behavior allowed false positive like: assert_template layout assert_template out/hello Now it only passes with: assert_template layout/hello assert_template hello Fixes #3849. *Hugolnx* * Handle `ActionDispatch::Http::UploadedFile` like `Rack::Test::UploadedFile`, don't call to_param on it. Since `Rack::Test::UploadedFile` isn't API compatible this is needed to test file uploads that rely on `tempfile` being available. *Tim Vandecasteele* * Fixed a bug with shorthand routes scoped with the `:module` option not adding the module to the controller as described in issue #6497. This should now work properly: scope :module = engine do get api/version # routes to engine/api#version end *Luiz Felipe Garcia Pereira* * Respect `config.digest = false` for `asset_path` Previously, the `asset_path` internals only respected the `:digest` option, but ignored the global config setting. This meant that `config.digest = false` could not be used in conjunction with `config.compile = false` this corrects the behavior. *Peter Wagenet* * Fix #7646, the log now displays the correct status code when an exception is raised
[Rails-core] Fwd: [ANN] Rails 3.2.9.rc3 has been released
Hi everyone, Rails 3.2.9.rc3 has been released. If no regressions are found I will release 3.2.9 final this Monday 12th. If you find a regression open an issue on github and mention me on it, mail me or tweet me, whatever but let me know :). ## CHANGES since 3.2.9.rc2 *Action Mailer* * No changes *Action Pack* * Lock sprockets to 2.2.x REASON: We had some pending fixes in sprockets and sass-rails to make possible to use sprockets version 2.2. We will do a more conservative sprockets upgrade for this release. In a next release we can relax the dependency again. See #8099 for more information. *Guillermo Iguaran* * Clear url helpers when reloading routes. *Santiago Pastorino* * Revert the shorthand routes scoped with `:module` option fix This added a regression since it is changing the URL mapping. This makes the stable release backward compatible. *Rafael Mendonça França* *Active Model* * No changes *Active Record* * No changes *Active Resource* * No changes *Active Support* * No changes *Railties* * Revert Respect children paths filter settings This reverts commit 53778ec2d716f860646fd43957fd53c8db4da2fe. Closes #8146 *Santiago Pastorino* ## SHA-1 * e830dbe5d93f6ea6ed8e32ac75e5c5a5dd4bd0fa actionmailer-3.2.9.rc3.gem * f50456d082164447d149540a144515877cd714b2 actionpack-3.2.9.rc3.gem * 60eca0f399779799e8ea7a8be6b68f3101fe5fe4 activemodel-3.2.9.rc3.gem * 0cfec8581690d4a6072c686464ddd66e80ac094e activerecord-3.2.9.rc3.gem * 5414975de41a1dfbb6dbd9cd74b53969c63f2e96 activeresource-3.2.9.rc3.gem * e67293cf746f315cc631155c28d3891a3532bb74 activesupport-3.2.9.rc3.gem * 8e62b4db1249024bbb1ea3a87fee701a0cfa5674 rails-3.2.9.rc3.gem * 6b4365046903bcd60c99f81bd48cccd1b3faae39 railties-3.2.9.rc3.gem You can find a list of changes between v3.2.9.rc2 and v3.2.9.rc3 [here](https://github.com/rails/rails/compare/v3.2.9.rc2...v3.2.9.rc3) and an exhaustive list of changes since v3.2.8 [here](https://github.com/rails/rails/compare/v3.2.8...v3.2.9.rc3). Thanks to everyone! -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.9.rc1 has been released
Senn* * `CollectionAssociation#count` returns `0` without querying if the parent record is not persisted. Before: person.pets.count # SELECT COUNT(*) FROM pets WHERE pets.person_id IS NULL # = 0 After: person.pets.count # fires without sql query # = 0 *Francesco Rodriguez* * Fix `reset_counters` crashing on `has_many :through` associations. Fix #7822. *lulalala* * ConnectionPool recognizes checkout_timeout spec key as taking precedence over legacy wait_timeout spec key, can be used to avoid conflict with mysql2 use of wait_timeout. Closes #7684. *jrochkind* * Rename field_changed? to _field_changed? so that users can create a field named field *Akira Matsuda*, backported by *Steve Klabnik* * Fix creation of through association models when using `collection=[]` on a `has_many :through` association from an unsaved model. Fix #7661. *Ernie Miller* * Explain only normal CRUD sql (select / update / insert / delete). Fix problem that explains unexplainable sql. Closes #7544 #6458. *kennyj* * Backport test coverage to ensure that PostgreSQL auto-reconnect functionality remains healthy. *Steve Jorgensen* * Use config['encoding'] instead of config['charset'] when executing databases.rake in the mysql/mysql2. A correct option for a database.yml is 'encoding'. *kennyj* * Fix ConnectionAdapters::Column.type_cast_code integer conversion, to always convert values to integer calling #to_i. Fixes #7509. *Thiago Pradi* * Fix time column type casting for invalid time string values to correctly return nil. *Adam Meehan* * Fix `becomes` when using a configured `inheritance_column`. *Yves Senn* * Fix `reset_counters` when there are multiple `belongs_to` association with the same foreign key and one of them have a counter cache. Fixes #5200. *Dave Desrochers* * Round usec when comparing timestamp attributes in the dirty tracking. Fixes #6975. *kennyj* * Use inversed parent for first and last child of has_many association. *Ravil Bayramgalin* * Fix Column.microseconds and Column.fast_string_to_date to avoid converting timestamp seconds to a float, since it occasionally results in inaccuracies with microsecond-precision times. Fixes #7352. *Ari Pollak* * Fix `increment!`, `decrement!`, `toggle!` that was skipping callbacks. Fixes #7306. *Rafael Mendonça França* * Fix AR#create to return an unsaved record when AR::RecordInvalid is raised. Fixes #3217. *Dave Yeu* * Remove unnecessary transaction when assigning has_one associations with a nil or equal value. Fix #7191. *kennyj* * Allow store to work with an empty column. Fix #4840. *Jeremy Walker* * Remove prepared statement from system query in postgresql adapter. Fix #5872. *Ivan Evtuhovich* * Make sure `:environment` task is executed before `db:schema:load` or `db:structure:load` Fixes #4772. *Seamus Abshere* *Active Resource* * No changes *Active Support* * Add logger.push_tags and .pop_tags to complement logger.tagged: class Job def before Rails.logger.push_tags :jobs, self.class.name end def after Rails.logger.pop_tags 2 end end *Jeremy Kemper* * Add %:z and %::z format string support to ActiveSupport::TimeWithZone#strftime. [fixes #6962] *kennyj* *Railties* * Don't eager-load app/assets and app/views *Elia Schito* * Update supported ruby versions error message in ruby_version_check.rb *Lihan Li* ## SHA-1 * 24af6eff6b7c647d04eee9585184ba89f0746d40 actionmailer-3.2.9.rc1.gem * c34ea8f12308c9f6fc4d6b31ce8caa2a562b210a actionpack-3.2.9.rc1.gem * 8b3171fdde905c76a541286192e6cef211d83a70 activemodel-3.2.9.rc1.gem * 0752e47880da4bb9be2b0309bce5a444a9271420 activerecord-3.2.9.rc1.gem * d8c1eeedbf3bc33d1560700cc70cb1752cdc811a activeresource-3.2.9.rc1.gem * 8ad917f70cc3b0a04864c8aa705a0e4997736872 activesupport-3.2.9.rc1.gem * 6fdc627a032f1f3ded7830e044298e20fd3fc6ce rails-3.2.9.rc1.gem * 444da0c3f2a1e3200d2a613973062c2d3e4ad7d0 railties-3.2.9.rc1.gem You can find a list of changes between v3.2.8 and v3.2.9.rc1 [here](https://github.com/rails/rails/compare/v3.2.8...v3.2.9.rc1) Thanks to everyone! -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] Test Locations in Rails 4
Mike, We decided to do this for Rails 4. Can you go ahead and provide a Pull Request?. Mention me on it and I will merge. Thanks again for putting all this ideas and for minitest-rails :) -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino On Sunday, September 30, 2012, Mike Moore wrote: On Sep 29, 2012, at 9:42 PM, Santiago Pastorino spastor...@gmail.com wrote: Hey Mike, Hey Santiago. I'm personally in favor of what you've proposed. I'm starting a discussion with other Rails core members about it. In case we decide to accept the changes we should be keeping compatibility with the old schema. Only new apps should be using this and old apps should continue working. We can probably show a message saying that there's a new directory schema for tests. What do you think?. Will you be able to provide a patch for all that?. Yep. The minitest-rails project has similar goals and is intended to live side-by-side with existing tests. The biggest issue is the rake tasks, but its certainly doable. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Test Locations in Rails 4
Hey Mike, I'm personally in favor of what you've proposed. I'm starting a discussion with other Rails core members about it. In case we decide to accept the changes we should be keeping compatibility with the old schema. Only new apps should be using this and old apps should continue working. We can probably show a message saying that there's a new directory schema for tests. What do you think?. Will you be able to provide a patch for all that?. Thank you very much for helping ;). -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino On Sat, Sep 29, 2012 at 2:32 PM, Mike Moore blowm...@gmail.com wrote: What do folks think about making changes to the default test locations? I would love to see the following changes made: test/units - test/models test/units/helpers - test/helpers test/units/lib - test/lib test/functional - test/controllers test/functional - test/mailers test/integration- test/acceptance I've already done this in minitest-rails for Rails 3, but I thought I'd check here before creating a pull request for Rails 4. Here is a blog I blogged on my blog explaining more about why I think this change is good. http://blowmage.com/2012/07/12/rails-tests-placement Thoughts? ~Mike -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.0.17 has been released!!!
Good news everyone! Rails version 3.0.17 has been released. This release of Rails contains three important security fixes: * [CVE-2012-3463 Ruby on Rails Potential XSS Vulnerability in select_tag prompt](https://groups.google.com/d/msg/rubyonrails-security/fV3QUToSMSw/eHBSFOUYHpYJ) * [CVE-2012-3464 Potential XSS Vulnerability in Ruby on Rails](https://groups.google.com/d/msg/rubyonrails-security/kKGNeMrnmiY/r2yM7xy-G48J) * [CVE-2012-3465 XSS Vulnerability in strip_tags](https://groups.google.com/d/msg/rubyonrails-security/FgVEtBajcTY/tYLS1JJTu38J) All changes can be found on [github](https://github.com/rails/rails/compare/v3.0.16...v3.0.17). Thanks everyone! -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.1.8 has been released!!!
Good news everyone! Rails version 3.1.8 has been released. This release of Rails contains three important security fixes: * [CVE-2012-3463 Ruby on Rails Potential XSS Vulnerability in select_tag prompt](https://groups.google.com/d/msg/rubyonrails-security/fV3QUToSMSw/eHBSFOUYHpYJ) * [CVE-2012-3464 Potential XSS Vulnerability in Ruby on Rails](https://groups.google.com/d/msg/rubyonrails-security/kKGNeMrnmiY/r2yM7xy-G48J) * [CVE-2012-3465 XSS Vulnerability in strip_tags](https://groups.google.com/d/msg/rubyonrails-security/FgVEtBajcTY/tYLS1JJTu38J) All changes can be found on [github](https://github.com/rails/rails/compare/v3.1.7...v3.1.8). Thanks everyone! -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.8 has been released!!!
Good news everyone! Rails version 3.2.8 has been released.
## IMPORTANT
This version contains three important security fixes, please upgrade
immediately.
* [CVE-2012-3463 Ruby on Rails Potential XSS Vulnerability in
select_tag
prompt](https://groups.google.com/d/msg/rubyonrails-security/fV3QUToSMSw/eHBSFOUYHpYJ)
* [CVE-2012-3464 Potential XSS Vulnerability in Ruby on
Rails](https://groups.google.com/d/msg/rubyonrails-security/kKGNeMrnmiY/r2yM7xy-G48J)
* [CVE-2012-3465 XSS Vulnerability in
strip_tags](https://groups.google.com/d/msg/rubyonrails-security/FgVEtBajcTY/tYLS1JJTu38J)
One of security fixes impacts all users and is related to HTML
escaping code. The other two fixes impacts people using select_tag's
prompt option and strip_tags helper from ActionPack.
We are also removing all the deprecation warnings that we introduced in 3.2.x.
We have decided to stop introducing API deprecations in all point
releases going forward. From now on, it'll only happen in
majors/minors.
## CHANGES since 3.2.7
*ActionMailer*
* No changes
*ActionPack*
* html_escape should escape single quotes. *Santiago Pastorino*
* Reverted the deprecation of `:confirm`. *Rafael Mendonça França*
* Reverted the deprecation of `:disable_with`. *Rafael Mendonça França*
* Reverted the deprecation of `:mouseover` option to `image_tag`.
*Rafael Mendonça França*
* Reverted the deprecation of `button_to_function` and
`link_to_function` helpers. *Rafael Mendonça França*
*ActiveModel*
* No changes
*ActiveRecord*
* Do not set RAILS_ENV to development when using `db:test:prepare`
and related rake tasks.
This was causing the truncation of the development database data
when using RSpec.
In RC2 was fixed again when using config.active_record.schema_format = :sql
*Rafael Mendonça França*
* Do not consider the numeric attribute as changed if the old value
is zero and the new value is not a string. Fixes #7237. *Rafael
Mendonça França*
* Removes the deprecation of `update_attribute`. *fxn*
* Reverted the deprecation of `composed_of`. *Rafael Mendonça França*
* Reverted the deprecation of `*_sql` association options. They will
be deprecated in 4.0 instead. *Jon Leighton*
* Do not eager load AR session store. ActiveRecord::SessionStore
depends on the abstract store
in Action Pack. Eager loading this class would break client code
that eager loads Active Record
standalone.
Fixes #7160
*Xavier Noria*
* Do not set RAILS_ENV to development when using `db:test:prepare`
and related rake tasks.
This was causing the truncation of the development database data
when using RSpec.
Fixes #7175.
*Rafael Mendonça França*
*ActiveResource*
* No changes
*ActiveSupport*
* Fix ActiveSupport integration with Mocha 0.12.1. *Mike Gunderloy*
* Reverted the deprecation of ActiveSupport::JSON::Variable. *Rafael
Mendonça França*
*Railties*
* ERB scaffold generator use the `:data = { :confirm = Text }`
syntax instead of `:confirm`. *Rafael Mendonça França*
## SHA-1
* 20525face84f3cdc8b0fc039e0f75ec4963e3677 actionmailer-3.2.8.gem
* ccc63cc2fcb3131b92d45cf5834aa629857d7258 actionpack-3.2.8.gem
* df7fb9febe248201fd1ad741a2044324f4c90cc9 activemodel-3.2.8.gem
* 96e876f625b98915d2b1994c06ea057bf7dd23b8 activerecord-3.2.8.gem
* 195e1e4653e6e06f469ea20e181727ef9d940ee7 activeresource-3.2.8.gem
* e5136f556b62343425cc147a8990bd043430354d activesupport-3.2.8.gem
* 35581ffc256d73d217537170b0e116cf4545752e rails-3.2.8.gem
* e44accc5d057866087856a521398250fe082b70b railties-3.2.8.gem
You can find an exhaustive list of changes on
[github](https://github.com/rails/rails/compare/v3.2.7...v3.2.8).
Thanks to everyone!
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.8.rc2 has been released
Hi everyone,
Rails 3.2.8.rc2 has been released. If no regressions are found we will
release 3.2.8 final around Wednesday 8th.
## IMPORTANT
We are removing all the deprecation warnings that we introduced in 3.2.x.
We have decided to stop introducing API deprecations in all point
releases going forward. From now on, it'll only happen in
majors/minors.
## CHANGES since 3.2.8.rc1
*ActionMailer*
* No changes
*ActionPack*
* html_escape should escape single quotes. *Santiago Pastorino*
*ActiveModel*
* No changes
*ActiveRecord*
* Do not set RAILS_ENV to development when using `db:test:prepare`
and related rake tasks.
This was causing the truncation of the development database data
when using RSpec.
In RC2 was fixed again when using config.active_record.schema_format = :sql
*Rafael Mendonça França*
* Do not consider the numeric attribute as changed if the old value
is zero and the new value is not a string. Fixes #7237. *Rafael
Mendonça França*
*ActiveResource*
* No changes
*ActiveSupport*
* Fix ActiveSupport integration with Mocha 0.12.1. *Mike Gunderloy*
*Railties*
* ERB scaffold generator use the `:data = { :confirm = Text }`
syntax instead of `:confirm`. *Rafael Mendonça França*
## SHA-1
* 351b13c792517534b68df02f550cfc335c8d3f5f actionmailer-3.2.8.rc2.gem
* 0b0f92bb3f2fad426f3b9c0849e5f5457c029586 actionpack-3.2.8.rc2.gem
* c19868c2f4fc20ebf20c1a27c89a65b80592b6e6 activemodel-3.2.8.rc2.gem
* 9d247e14feb6d453aded4ba9edc8bae1cf940891 activerecord-3.2.8.rc2.gem
* 7db76b428fdec2aeea190773d5daea139c7732ba activeresource-3.2.8.rc2.gem
* b93d62722c854fde8acda511f53481c4f3ceeaf2 activesupport-3.2.8.rc2.gem
* 7fd2e2035469e89e17b3872d51968a5856d6ed8c rails-3.2.8.rc2.gem
* bf685a73a55fd5ffa77c7c0160b2bec898fa15eb railties-3.2.8.rc2.gem
You can find a list of changes between v3.2.8.rc1 and v3.2.8.rc2
[here](https://github.com/rails/rails/compare/v3.2.8.rc1...v3.2.8.rc2)
and an exhaustive list of changes since v3.2.7
[here](https://github.com/rails/rails/compare/v3.2.7...v3.2.8.rc2).
Please let us know if your test suites are fine with this release or not.
Thanks to everyone!
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.8.rc1 has been released
Hi everyone, Rails 3.2.8.rc1 has been released. If no regressions are found we will release 3.2.8 final on Friday. ## IMPORTANT We are removing all the deprecation warnings that we introduced in 3.2.x. We have decided to stop introducing API deprecations in all point releases going forward. From now on, it'll only happen in majors/minors. ## CHANGES since 3.2.7 *ActionMailer* * No changes *ActionPack* * Reverted the deprecation of `:confirm`. *Rafael Mendonça França* * Reverted the deprecation of `:disable_with`. *Rafael Mendonça França* * Reverted the deprecation of `:mouseover` option to `image_tag`. *Rafael Mendonça França* * Reverted the deprecation of `button_to_function` and `link_to_function` helpers. *Rafael Mendonça França* *ActiveModel* * No changes *ActiveRecord* * Removes the deprecation of `update_attribute`. *fxn* * Reverted the deprecation of `composed_of`. *Rafael Mendonça França* * Reverted the deprecation of `*_sql` association options. They will be deprecated in 4.0 instead. *Jon Leighton* * Do not eager load AR session store. ActiveRecord::SessionStore depends on the abstract store in Action Pack. Eager loading this class would break client code that eager loads Active Record standalone. Fixes #7160 *Xavier Noria* * Do not set RAILS_ENV to development when using `db:test:prepare` and related rake tasks. This was causing the truncation of the development database data when using RSpec. Fixes #7175. *Rafael Mendonça França* * update_columns added. *Sebastián Martínez* *ActiveResource* * No changes *ActiveSupport* * Reverted the deprecation of ActiveSupport::JSON::Variable. *Rafael Mendonça França* *Railties* * No changes ## SHA-1 * MD5 (actionmailer-3.2.8.rc1.gem) = 2e12c71925f8f7f5f05e3225f80e9359db8b0401 * MD5 (actionpack-3.2.8.rc1.gem) = d6947496fb560393d7eeb18fbb77e7ee2dff2a37 * MD5 (activemodel-3.2.8.rc1.gem) = 4be43d52aa3af70f154101b605ac80c45f0b68ff * MD5 (activerecord-3.2.8.rc1.gem) = 84bc989af7f1bd2e9320fa39d80ca783e3499e94 * MD5 (activeresource-3.2.8.rc1.gem) = 0ba8e537711adabd81fec69f4762a32c5ceb381c * MD5 (activesupport-3.2.8.rc1.gem) = 74c2445d8d2541e04e10a969d2ce14419ee3bb9d * MD5 (rails-3.2.8.rc1.gem) = 470bc8d4402b44e9f5f82f0610d31e6e6945b897 * MD5 (railties-3.2.8.rc1.gem) = b615346580471aa6dcf338826824f78d0aec8512 You can find an exhaustive list of changes on [github](https://github.com/rails/rails/compare/v3.2.7…v3.2.8.rc1). Thanks to everyone! -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] Re: [ANN] Rails 3.2.8.rc1 has been released
Quick correction ... This * update_columns added. *Sebastián Martínez* Was never added. On Wed, Aug 1, 2012 at 6:00 PM, Santiago Pastorino santi...@wyeworks.com wrote: Hi everyone, Rails 3.2.8.rc1 has been released. If no regressions are found we will release 3.2.8 final on Friday. ## IMPORTANT We are removing all the deprecation warnings that we introduced in 3.2.x. We have decided to stop introducing API deprecations in all point releases going forward. From now on, it'll only happen in majors/minors. ## CHANGES since 3.2.7 *ActionMailer* * No changes *ActionPack* * Reverted the deprecation of `:confirm`. *Rafael Mendonça França* * Reverted the deprecation of `:disable_with`. *Rafael Mendonça França* * Reverted the deprecation of `:mouseover` option to `image_tag`. *Rafael Mendonça França* * Reverted the deprecation of `button_to_function` and `link_to_function` helpers. *Rafael Mendonça França* *ActiveModel* * No changes *ActiveRecord* * Removes the deprecation of `update_attribute`. *fxn* * Reverted the deprecation of `composed_of`. *Rafael Mendonça França* * Reverted the deprecation of `*_sql` association options. They will be deprecated in 4.0 instead. *Jon Leighton* * Do not eager load AR session store. ActiveRecord::SessionStore depends on the abstract store in Action Pack. Eager loading this class would break client code that eager loads Active Record standalone. Fixes #7160 *Xavier Noria* * Do not set RAILS_ENV to development when using `db:test:prepare` and related rake tasks. This was causing the truncation of the development database data when using RSpec. Fixes #7175. *Rafael Mendonça França* * update_columns added. *Sebastián Martínez* *ActiveResource* * No changes *ActiveSupport* * Reverted the deprecation of ActiveSupport::JSON::Variable. *Rafael Mendonça França* *Railties* * No changes ## SHA-1 * MD5 (actionmailer-3.2.8.rc1.gem) = 2e12c71925f8f7f5f05e3225f80e9359db8b0401 * MD5 (actionpack-3.2.8.rc1.gem) = d6947496fb560393d7eeb18fbb77e7ee2dff2a37 * MD5 (activemodel-3.2.8.rc1.gem) = 4be43d52aa3af70f154101b605ac80c45f0b68ff * MD5 (activerecord-3.2.8.rc1.gem) = 84bc989af7f1bd2e9320fa39d80ca783e3499e94 * MD5 (activeresource-3.2.8.rc1.gem) = 0ba8e537711adabd81fec69f4762a32c5ceb381c * MD5 (activesupport-3.2.8.rc1.gem) = 74c2445d8d2541e04e10a969d2ce14419ee3bb9d * MD5 (rails-3.2.8.rc1.gem) = 470bc8d4402b44e9f5f82f0610d31e6e6945b897 * MD5 (railties-3.2.8.rc1.gem) = b615346580471aa6dcf338826824f78d0aec8512 You can find an exhaustive list of changes on [github](https://github.com/rails/rails/compare/v3.2.7…v3.2.8.rc1). Thanks to everyone! -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] rails-api was released!!!
The project url is https://github.com/spastorino/rails-api and you can read more info about it on this blog post http://blog.wyeworks.com/2012/4/20/rails-for-api-applications-rails-api-released Please test it, and share the performance improvements you may get. This is REALLY important if this plugin show real improvements the whole thing could be added to core. Cheers, Santiago. -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.3 was released!!!
Rails 3.2.3 has been released!!!.
### IMPORTANT
This release changes the default value of
*config.active_record.whitelist_attributes* to true. This change only
affects newly generated applications so it should not cause any
backwards compatibility issues for users who are upgrading but it may
affect some tutorials and introductory material. For more information
see the mass assignment section of the [ruby on rails security
guide][1]
Rails 3.2.3 also introduces a new option that allows you to control
the behavior of remote forms when it comes to `authenticity_token`
generation. If you want to fragment cache your forms, authenticity
token will also get cached, which isn't acceptable. However, if you
only use such forms with ajax, you can disable token generation,
because it will be fetched from `meta` tag. Starting with 3.2.3, you
have an option to stop generating `authenticity_token` in remote forms
(ie. `:remote = true` is passed as an option), by setting
`config.action_view.embed_authenticity_token_in_remote_forms = false`.
Please note that this will break sending those forms with javascript
disabled. If you choose to not generate the token in remote forms by
default, you can still explicitly pass `:authenticity_token = true`
when generating the form to bypass this setting.
The option defaults to `true`, which means that existing apps are
*NOT* affected.
We've also adjusted the dependencies on rack-cache and mail to address
the recent security vulnerabilities with those libraries. If you are
running a vulnerable version of mail or rack-cache you should update
both gems to a safe version. There were also some regressions in the
render method that were fixed in this version.
[1]: http://guides.rubyonrails.org/security.html#mass-assignment
### CHANGES since 3.2.2
*Action Mailer*
* Upgrade mail version to 2.4.3 *ML*
*Action Pack*
* Fix #5632, render :inline set the proper rendered format.
*Santiago Pastorino*
* Fix textarea rendering when using plugins like HAML. Such plugins
encode the first newline character in the content. This issue was
introduced in https://github.com/rails/rails/pull/5191 *James Coleman*
* Do not include the authenticity token in forms where remote: true
as ajax forms use the meta-tag value *DHH*
* Turn off verbose mode of rack-cache, we still have X-Rack-Cache to
check that info. Closes #5245. *Santiago Pastorino*
* Fix #5238, rendered_format is not set when template is not
rendered. *Piotr Sarnacki*
* Upgrade rack-cache to 1.2. *José Valim*
* ActionController::SessionManagement is deprecated. *Santiago Pastorino*
* Since the router holds references to many parts of the system like
engines, controllers and the application itself, inspecting the route
set can actually be really slow, therefore we default alias inspect to
to_s. *José Valim*
* Add a new line after the textarea opening tag. Closes #393 *rafaelfranca*
* Always pass a respond block from to responder. We should let the
responder to decide what to do with the given overridden response
block, and not short circuit it. *sikachu*
* Fixes layout rendering regression from 3.2.2. *José Valim*
*Active Model*
* No changes
*Active Record*
* Added find_or_create_by_{attribute}! dynamic method. *Andrew White*
* Whitelist all attribute assignment by default. Change the default
for newly generated applications to whitelist all attribute
assignment. Also update the generated model classes so users are
reminded of the importance of attr_accessible. *NZKoz*
* Update ActiveRecord::AttributeMethods#attribute_present? to return
false for empty strings. *Jacobkg*
* Fix associations when using per class databases. *larskanis*
* Revert setting NOT NULL constraints in add_timestamps *fxn*
* Fix mysql to use proper text types. Fixes #3931. *kennyj*
* Fix #5069 - Protect foreign key from mass assignment through
association builder. *byroot*
*Active Resource*
* No changes
*Active Support*
* No changes
*Railties*
* No changes
### SHA-1
* SHA-1 (actionmailer-3.2.3.gem) = 04cd2772dd2d402ffb9d9dbf70f5f2256c598ab3
* SHA-1 (actionpack-3.2.3.gem) = 06d51ebd0863e0075d9a3e89a2e48dcc262c4e0c
* SHA-1 (activemodel-3.2.3.gem) = 3f648213b88bb3695e2bce38ff823be99535f401
* SHA-1 (activerecord-3.2.3.gem) = a9810e79d720994abbe24aded2bcb783bb1649b4
* SHA-1 (activeresource-3.2.3.gem) = 3d1de8a80122efbcf6c8b8dfc13a7ab644bb2ca3
* SHA-1 (activesupport-3.2.3.gem) = 6a63d75c798fb87d081cbee9323c46bec4727490
* SHA-1 (rails-3.2.3.gem) = 4db7e5c288f5260dc299d55ec2aad9a330b611fc
* SHA-1 (railties-3.2.3.gem) = 39a887de71350ece12c784d3764b7be2c6659b32
You can find an exhaustive list of changes made between 3.2.2 and
3.2.3 [here](https://github.com/rails/rails/compare/v3.2.2...v3.2.3).
Thanks to everyone for making this possible and enjoy it :).
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
[Rails-core] [ANN] Rails 3.2.3.rc2 was released!
Rails 3.2.3.rc2 has been released. ### IMPORTANT Rails 3.2.3 introduced a new option that allows you to control the behavior of remote forms when it comes to `authenticity_token` generation. If you want to fragment cache your forms, authenticity token will also get cached, which isn't acceptable. However, if you only use such forms with ajax, you can disable token generation, because it will be fetched from `meta` tag. Starting with 3.2.3, you have an option to stop generating `authenticity_token` in remote forms (ie. `:remote = true` is passed as an option), by setting `config.action_view.embed_authenticity_token_in_remote_forms = false`. Please note that this will break sending those forms with javascript disabled. If you choose to not generate the token in remote forms by default, you can still explicitly pass `:authenticity_token = true` when generating the form to bypass this setting. The option defaults to `true`, which means that existing apps are *NOT* affected. This RC includes this authenticity_token change and 2 bug fixes described below. If there are no more release blockers, I will be releasing the final version on March 30th (tomorrow). If you find something please open an issue on github and let me know through email (santiago _at_ wyeworks.com), tweet ([spastorino](http://twitter.com/spastorino)) or cc me on the github issue. ### CHANGES since 3.2.3.rc1 *Action Mailer* * No changes *Action Pack* * Fix #5632, render :inline set the proper rendered format. *Santiago Pastorino* * Fix textarea rendering when using plugins like HAML. Such plugins encode the first newline character in the content. This issue was introduced in https://github.com/rails/rails/pull/5191 *James Coleman* *Active Model* * No changes *Active Record* * No changes *Active Resource* * No changes *Active Support* * No changes *Railties* * No changes ### SHA-1 * SHA-1 (actionmailer-3.2.3.rc2.gem) = * SHA-1 (actionpack-3.2.3.rc2.gem) = * SHA-1 (activemodel-3.2.3.rc2.gem) = * SHA-1 (activerecord-3.2.3.rc2.gem) = * SHA-1 (activeresource-3.2.3.rc2.gem) = * SHA-1 (activesupport-3.2.3.rc2.gem) = * SHA-1 (rails-3.2.3.rc2.gem) = * SHA-1 (railties-3.2.3.rc2.gem) = You can find the list of all changes made between 3.2.3.rc1 and 3.2.3.rc2 [here](https://github.com/rails/rails/compare/v3.2.3.rc1...v3.2.3.rc2) and an exhaustive list of changes between 3.2.2 and 3.2.3.rc2 [here](https://github.com/rails/rails/compare/v3.2.2...v3.2.3.rc2). Thanks to everyone, this is your last chance to hold the release if something goes wrong. So please, give this release a try :). -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.3.rc1 was released!
Rails 3.2.3.rc1 has been released.
### IMPORTANT
This release changes the default value of
*config.active_record.whitelist_attributes* to true. This change only
affects newly generated applications so it should not cause any
backwards compatibility issues for users who are upgrading but it may
affect some tutorials and introductory material. For more information
see the mass assignment section of the [ruby on rails security
guide][1]
We've also adjusted the dependencies on rack-cache and mail to address
the recent security vulnerabilities with those libraries. If you are
running a vulnerable version of mail or rack-cache you should update
both gems to a safe version. We also fixed a couple of regressions in
the render method.
If there are no release blockers, then I will be releasing the final
version on March 29th.
If you find something please open an issue on github and let me know
through email (santiago _at_ wyeworks.com), tweet
([spastorino](http://twitter.com/spastorino)) or cc me on the github
issue.
[1]: http://guides.rubyonrails.org/security.html#mass-assignment
### CHANGES since 3.2.2
*ActionMailer*
* Upgrade mail version to 2.4.3 *ML*
*ActionPack*
* Do not include the authenticity token in forms where remote: true
as ajax forms use the meta-tag value *DHH*
* Turn off verbose mode of rack-cache, we still have X-Rack-Cache to
check that info. Closes #5245. *Santiago Pastorino*
* Fix #5238, rendered_format is not set when template is not
rendered. *Piotr Sarnacki*
* Upgrade rack-cache to 1.2. *José Valim*
* ActionController::SessionManagement is deprecated. *Santiago Pastorino*
* Since the router holds references to many parts of the system like
engines, controllers and the application itself, inspecting the route
set can actually be really slow, therefore we default alias inspect to
to_s. *José Valim*
* Add a new line after the textarea opening tag. Closes #393 *rafaelfranca*
* Always pass a respond block from to responder. We should let the
responder to decide what to do with the given overridden response
block, and not short circuit it. *sikachu*
* Fixes layout rendering regression from 3.2.2. *José Valim*
*ActiveModel*
* No changes
*ActiveRecord*
* Added find_or_create_by_{attribute}! dynamic method. *Andrew White*
* Whitelist all attribute assignment by default. Change the default
for newly generated applications to whitelist all attribute
assignment. Also update the generated model classes so users are
reminded of the importance of attr_accessible. *NZKoz*
* Update ActiveRecord::AttributeMethods#attribute_present? to return
false for empty strings. *Jacobkg*
* Fix associations when using per class databases. *larskanis*
* Revert setting NOT NULL constraints in add_timestamps *fxn*
* Fix mysql to use proper text types. Fixes #3931. *kennyj*
* Fix #5069 - Protect foreign key from mass assignment through
association builder. *byroot*
*ActiveResource*
* No changes
*ActiveSupport*
* No changes
*Railties*
* No changes
### SHA-1
* SHA-1 (actionmailer-3.2.3.rc1.gem) = 6e945a152d2159918f05dcf4ef72e87d4b75c2bb
* SHA-1 (actionpack-3.2.3.rc1.gem) = 1c5153c4b4865207193d7e8af9a09b493683bc55
* SHA-1 (activemodel-3.2.3.rc1.gem) = eae6bb4cc275e167eb28b35cd8b0a46466dd3c88
* SHA-1 (activerecord-3.2.3.rc1.gem) = 8a2709c7517d9d91911ad3fbfe82af19422b5e24
* SHA-1 (activeresource-3.2.3.rc1.gem) =
770a7120f8148f6391a717c03f08cdb76dcd64ac
* SHA-1 (activesupport-3.2.3.rc1.gem) = 1e89864fc28c7b8cca67eb93696f1b2ecf556b81
* SHA-1 (rails-3.2.3.rc1.gem) = b1dec2b8c59c78111479e3dc36c106e54fe11f1a
* SHA-1 (railties-3.2.3.rc1.gem) = 9fbbb616cd868d1070bf04adeda50c373550c349
You can find an exhaustive list of changes on
[github](https://github.com/rails/rails/compare/v3.2.2...v3.2.3.rc1).
Thanks to everyone, this is your last chance to hold the release if
something goes wrong. So please, give this release a try :).
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] Re: [ANN] Rails 3.2.3.rc1 was released!
Just a minor fix, I will release the final version on March 30th
On Tue, Mar 27, 2012 at 2:17 PM, Santiago Pastorino
santi...@wyeworks.com wrote:
Rails 3.2.3.rc1 has been released.
### IMPORTANT
This release changes the default value of
*config.active_record.whitelist_attributes* to true. This change only
affects newly generated applications so it should not cause any
backwards compatibility issues for users who are upgrading but it may
affect some tutorials and introductory material. For more information
see the mass assignment section of the [ruby on rails security
guide][1]
We've also adjusted the dependencies on rack-cache and mail to address
the recent security vulnerabilities with those libraries. If you are
running a vulnerable version of mail or rack-cache you should update
both gems to a safe version. We also fixed a couple of regressions in
the render method.
If there are no release blockers, then I will be releasing the final
version on March 29th.
If you find something please open an issue on github and let me know
through email (santiago _at_ wyeworks.com), tweet
([spastorino](http://twitter.com/spastorino)) or cc me on the github
issue.
[1]: http://guides.rubyonrails.org/security.html#mass-assignment
### CHANGES since 3.2.2
*ActionMailer*
* Upgrade mail version to 2.4.3 *ML*
*ActionPack*
* Do not include the authenticity token in forms where remote: true
as ajax forms use the meta-tag value *DHH*
* Turn off verbose mode of rack-cache, we still have X-Rack-Cache to
check that info. Closes #5245. *Santiago Pastorino*
* Fix #5238, rendered_format is not set when template is not
rendered. *Piotr Sarnacki*
* Upgrade rack-cache to 1.2. *José Valim*
* ActionController::SessionManagement is deprecated. *Santiago Pastorino*
* Since the router holds references to many parts of the system like
engines, controllers and the application itself, inspecting the route
set can actually be really slow, therefore we default alias inspect to
to_s. *José Valim*
* Add a new line after the textarea opening tag. Closes #393 *rafaelfranca*
* Always pass a respond block from to responder. We should let the
responder to decide what to do with the given overridden response
block, and not short circuit it. *sikachu*
* Fixes layout rendering regression from 3.2.2. *José Valim*
*ActiveModel*
* No changes
*ActiveRecord*
* Added find_or_create_by_{attribute}! dynamic method. *Andrew White*
* Whitelist all attribute assignment by default. Change the default
for newly generated applications to whitelist all attribute
assignment. Also update the generated model classes so users are
reminded of the importance of attr_accessible. *NZKoz*
* Update ActiveRecord::AttributeMethods#attribute_present? to return
false for empty strings. *Jacobkg*
* Fix associations when using per class databases. *larskanis*
* Revert setting NOT NULL constraints in add_timestamps *fxn*
* Fix mysql to use proper text types. Fixes #3931. *kennyj*
* Fix #5069 - Protect foreign key from mass assignment through
association builder. *byroot*
*ActiveResource*
* No changes
*ActiveSupport*
* No changes
*Railties*
* No changes
### SHA-1
* SHA-1 (actionmailer-3.2.3.rc1.gem) =
6e945a152d2159918f05dcf4ef72e87d4b75c2bb
* SHA-1 (actionpack-3.2.3.rc1.gem) = 1c5153c4b4865207193d7e8af9a09b493683bc55
* SHA-1 (activemodel-3.2.3.rc1.gem) = eae6bb4cc275e167eb28b35cd8b0a46466dd3c88
* SHA-1 (activerecord-3.2.3.rc1.gem) =
8a2709c7517d9d91911ad3fbfe82af19422b5e24
* SHA-1 (activeresource-3.2.3.rc1.gem) =
770a7120f8148f6391a717c03f08cdb76dcd64ac
* SHA-1 (activesupport-3.2.3.rc1.gem) =
1e89864fc28c7b8cca67eb93696f1b2ecf556b81
* SHA-1 (rails-3.2.3.rc1.gem) = b1dec2b8c59c78111479e3dc36c106e54fe11f1a
* SHA-1 (railties-3.2.3.rc1.gem) = 9fbbb616cd868d1070bf04adeda50c373550c349
You can find an exhaustive list of changes on
[github](https://github.com/rails/rails/compare/v3.2.2...v3.2.3.rc1).
Thanks to everyone, this is your last chance to hold the release if
something goes wrong. So please, give this release a try :).
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Please, keep changing!
Just to say that we shouldn't care when people try to offend, BUT even if someone is doing that we should definitely listen to critics, try to improve what is wrong and not being :emo: about that. Anyway I didn't find any of the posts as personal attacks or bad suited but perhaps is just me. Cheers. -- Santiago Pastorino WyeWorks Co-founder http://www.wyeworks.com Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino On Thu, Mar 1, 2012 at 6:03 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Em 01-03-2012 16:59, James B. Byrne escreveu: On Thursday, 1 March 2012 at 15:52, Rodrigo Rosenfeld Rosas wrote: I've been reading lots of articles criticizing Rails in the last days. What articles are those? The most recent and famous ones are: http://gilesbowkett.blogspot.com/2012/02/rails-went-off-rails-why-im-rebuilding.html http://merbist.com/2012/02/29/learning-from-rails-failures/ I do respect their opinion. I just think I should state my opinion too so that their opinion don't become the only one. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.2.0.rc2 has been released
Hi everyone,
Rails 3.2.0.rc2 has been released. **Update your Gemfile to depend on
sass-rails ~ 3.2.3**
## IMPORTANT
**Support for Rails 2.3-style plugins (vendor/plugins!) will be
removed in Rails 4.0. Move them out and bundle them in your Gemfile,
or fold them in to your app as lib/myplugin/* and
config/initializers/myplugin.rb**
## CHANGES since RC1
*ActionMailer*
* No changes
*ActionPack*
* Add font_path helper method **Santiago Pastorino**
* Depends on rack ~ 1.4.0 **Santiago Pastorino**
* Add :gzip option to `caches_page`. The default option can be
configured globally using `page_cache_compression` **Andrey Sitnik**
*ActiveModel*
* No changes
*ActiveRecord*
* No changes
*ActiveResource*
* No changes
*ActiveSupport*
* ActiveSupport::Base64 is deprecated in favor of ::Base64. **Sergey
Nartimov**
*Railties*
* Rails 2.3-style plugins in vendor/plugins are deprecated and will
be removed in Rails 4.0. Move them out of vendor/plugins and bundle
them in your Gemfile, or fold them in to your app as lib/myplugin/*
and config/initializers/myplugin.rb. **Santiago Pastorino**
* Guides are available as a single .mobi for the Kindle and free
Kindle readers apps. **Michael Pearson Xavier Noria**
* Allow scaffold/model/migration generators to accept a index and
uniq modifiers, as in: tracking_id:integer:uniq in order to
generate (unique) indexes. Some types also accept custom options, for
instance, you can specify the precision and scale for decimals as
price:decimal{7,2}. **Dmitrii Samoilov**
## SHA-1
* MD5 (actionmailer-3.2.0.rc2.gem) = 118c83b2cddaa935d1de7534cfb6c810
* MD5 (actionpack-3.2.0.rc2.gem) = 6b18851bc26d5c8958672f27adda05ca
* MD5 (activemodel-3.2.0.rc2.gem) = d82f4eed949dcff17f8bf2aed806679a
* MD5 (activerecord-3.2.0.rc2.gem) = d07806fd5fc464f960200d20ceb2193a
* MD5 (activeresource-3.2.0.rc2.gem) = f51af240ff4623b0b6f8a4293ffa50dc
* MD5 (activesupport-3.2.0.rc2.gem) = 01380240c12e0380c9e61c97dd45f2f1
* MD5 (rails-3.2.0.rc2.gem) = 134f923f7d821f514abf6bdf4af62ca7
* MD5 (railties-3.2.0.rc2.gem) = 4b3ac0f9c5da16b90a1875e8199253d2
You can find an exhaustive list of changes on
[github](https://github.com/rails/rails/compare/v3.2.0.rc1...v3.2.0.rc2).
Along with the [closed issues marked for
v3.2.0](https://github.com/rails/rails/issues?milestone=3state=closed).
You can also see issues [we haven't closed
yet](https://github.com/rails/rails/issues?milestone=3state=open).
Thanks to everyone!
--
Santiago Pastorino
WyeWorks Co-founder
http://www.wyeworks.com
Twitter: http://twitter.com/spastorino
Github: http://github.com/spastorino
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.1.1 has been released!
Hi everyone,
Rails 3.1.1 has been released.
## CHANGES
*ActionMailer*
* No changes
*ActionPack*
* stylesheet_link_tag('/stylesheets/application') and similar helpers doesn't
throw Sprockets::FileOutsidePaths exception anymore [Santiago Pastorino]
* Ensure default_asset_host_protocol is respected, closes #2980. [José Valim]
Changing rake db:schema:dump to run :environment as well as :load_config,
as running :load_config alone will lead to the dumper being run without
including extensions such as those included in foreigner and
spatial_adapter.
This reverses a change made here:
https://github.com/rails/rails/commit/5df72a238e9fcb18daf6ab6e6dc9051c9106d7bb#L0L324
I'm assuming here that :load_config needs to be invoked
separately from :environment, as it is elsewhere in the
file for db operations, if not the alternative is to go
back to task :dump = :environment do.
[Ben Woosley]
* Update to rack-cache 1.1.
Versions prior to 1.1 delete the If-Modified-Since and If-Not-Modified
headers when config.action_controller.perform_caching is true. This has two
problems:
* unexpected inconsistent behaviour between development
production environments
* breaks applications that use of these headers
[Brendan Ribera]
* Ensure that enhancements to assets:precompile task are only run once
[Sam Pohlenz]
* TestCase should respect the view_assigns API instead of pulling variables on
its own. [José Valim]
* javascript_path and stylesheet_path now refer to /assets if asset pipelining
is on. [Santiago Pastorino]
* button_to support form option. Now you're able to pass for example
'data-type' = 'json'. [ihower]
* image_path and image_tag should use /assets if asset pipelining is turned
on. Closes #3126 [Santiago Pastorino and christos]
* Avoid use of existing precompiled assets during rake assets:precompile run.
Closes #3119 [Guillermo Iguaran]
* Copy assets to nondigested filenames too [Santiago Pastorino]
* Give precedence to `config.digest = false` over the existence of
manifest.yml asset digests [christos]
* escape options for the stylesheet_link_tag method [Alexey Vakhov]
* Re-launch assets:precompile task using (Rake.)ruby instead of Kernel.exec so
it works on Windows [cablegram]
* env var passed to process shouldn't be modified in process method. [Santiago
Pastorino]
* `rake assets:precompile` loads the application but does not initialize
it.
To the app developer, this means configuration add in
config/initializers/* will not be executed.
Plugins developers need to special case their initializers that are
meant to be run in the assets group by adding :group = :assets. [José Valim]
* Sprockets uses config.assets.prefix for asset_path [asee]
* FileStore key_file_path properly limit filenames to 255 characters.
[phuibonhoa]
* Fix Hash#to_query edge case with html_safe strings. [brainopia]
* Allow asset tag helper methods to accept :digest = false option in
order to completely avoid the digest generation.
Useful for linking assets from static html files or from emails when the user
could probably look at an older html email with an older asset.
[Santiago Pastorino]
* Don't mount Sprockets server at config.assets.prefix if
config.assets.compile is false. [Mark J. Titorenko]
* Set relative url root in assets when controller isn't available for
Sprockets (eg. Sass files using asset_path). Fixes #2435 [Guillermo
Iguaran]
* Fix basic auth credential generation to not make newlines. GH #2882
* Fixed the behavior of asset pipeline when config.assets.digest and
config.assets.compile are false and requested asset isn't precompiled.
Before the requested asset were compiled anyway ignoring that the
config.assets.compile flag is false. [Guillermo Iguaran]
* CookieJar is now Enumerable. Fixes #2795
* Fixed AssetNotPrecompiled error raised when rake assets:precompile
is compiling certain .erb files. See GH #2763 #2765 #2805 [Guillermo
Iguaran]
* Manifest is correctly placed in assets path when default assets
prefix is changed. Fixes #2776 [Guillermo Iguaran]
* Fixed stylesheet_link_tag and javascript_include_tag to respect
additional options passed by the users when debug is on. [Guillermo
Iguaran]
* Fix ActiveRecord#exists? when passsed a nil value
* Fix assert_select_email to work on multipart and non-multipart
emails as the method stopped working correctly in Rails 3.x due to
changes in the new mail gem.
*ActiveModel*
* Remove hard dependency on bcrypt-ruby to avoid make ActiveModel
dependent on a binary library.
You must add the gem explicitly to your Gemfile if you want use
ActiveModel::SecurePassword:
gem 'bcrypt-ruby', '~ 3.0.0'
See GH #2687. [Guillermo Iguaran]
*ActiveRecord*
* Add deprecation for the preload_associations method. Fixes #3022.
[Jon Leighton]
* Don't require a DB connection when loading a model that uses
set_primary_key. GH #2807.
[Jon Leighton]
* Fix using select() with a habtm association, e.g
Re: [Rails-core] Running tests on master
Check against http://travis-ci.org/#!/rails/rails/ On Fri, Oct 7, 2011 at 5:39 PM, drummondj j.drumm...@hotmail.co.uk wrote: Hi All, I followed the instructions in http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html but I get 21 errors and 1 failure (excluding AR because I haven't set it up yet). This is not expected is it? Many thanks, John. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] [ANN] Rails 3.1.1.rc3
Can you provide a fix for it?.
Thanks.
On Thu, Oct 6, 2011 at 10:03 AM, Yury Korolev yury.koro...@gmail.com wrote:
Hello
I know, it is not regression, but this
issue https://github.com/rails/rails/issues/3164 is very annoying.
On Thu, Oct 6, 2011 at 6:36 AM, Santiago Pastorino santi...@wyeworks.com
wrote:
Hi everyone,
Rails 3.1.1.rc3 has been released. Please give it a try, it's our
chance to fix regressions you might find and make a beautiful 3.1.1
stable release. If there are no regressions I will be releasing 3.1.1
final next October 7th. If you find any regression please contact me
ASAP by email, twitter or github.
## CHANGES
*ActionMailer*
* No changes
*ActionPack*
* stylesheet_link_tag('/stylesheets/application') and similar helpers
doesn't
throw Sprockets::FileOutsidePaths exception anymore [Santiago Pastorino]
* Ensure default_asset_host_protocol is respected, closes #2980. [José
Valim]
Changing rake db:schema:dump to run :environment as well as :load_config,
as running :load_config alone will lead to the dumper being run without
including extensions such as those included in foreigner and
spatial_adapter.
This reverses a change made here:
https://github.com/rails/rails/commit/5df72a238e9fcb18daf6ab6e6dc9051c9106d7bb#L0L324
I'm assuming here that :load_config needs to be invoked
separately from :environment, as it is elsewhere in the
file for db operations, if not the alternative is to go
back to task :dump = :environment do.
[Ben Woosley]
* Update to rack-cache 1.1.
Versions prior to 1.1 delete the If-Modified-Since and If-Not-Modified
headers when config.action_controller.perform_caching is true. This has
two
problems:
* unexpected inconsistent behaviour between development
production environments
* breaks applications that use of these headers
[Brendan Ribera]
* Ensure that enhancements to assets:precompile task are only run once
[Sam Pohlenz]
* TestCase should respect the view_assigns API instead of pulling
variables on
its own. [José Valim]
* javascript_path and stylesheet_path now refer to /assets if asset
pipelining
is on. [Santiago Pastorino]
* button_to support form option. Now you're able to pass for example
'data-type' = 'json'. [ihower]
* image_path and image_tag should use /assets if asset pipelining is
turned
on. Closes #3126 [Santiago Pastorino and christos]
* Avoid use of existing precompiled assets during rake assets:precompile
run.
Closes #3119 [Guillermo Iguaran]
* Copy assets to nondigested filenames too [Santiago Pastorino]
* Give precedence to `config.digest = false` over the existence of
manifest.yml asset digests [christos]
* escape options for the stylesheet_link_tag method [Alexey Vakhov]
* Re-launch assets:precompile task using (Rake.)ruby instead of
Kernel.exec so
it works on Windows [cablegram]
* env var passed to process shouldn't be modified in process method.
[Santiago
Pastorino]
* `rake assets:precompile` loads the application but does not initialize
it.
To the app developer, this means configuration add in
config/initializers/* will not be executed.
Plugins developers need to special case their initializers that are
meant to be run in the assets group by adding :group = :assets. [José
Valim]
* Sprockets uses config.assets.prefix for asset_path [asee]
* FileStore key_file_path properly limit filenames to 255 characters.
[phuibonhoa]
* Fix Hash#to_query edge case with html_safe strings. [brainopia]
* Allow asset tag helper methods to accept :digest = false option in
order to completely avoid the digest generation.
Useful for linking assets from static html files or from emails when the
user
could probably look at an older html email with an older asset.
[Santiago Pastorino]
* Don't mount Sprockets server at config.assets.prefix if
config.assets.compile is false. [Mark J. Titorenko]
* Set relative url root in assets when controller isn't available for
Sprockets (eg. Sass files using asset_path). Fixes #2435 [Guillermo
Iguaran]
* Fix basic auth credential generation to not make newlines. GH #2882
* Fixed the behavior of asset pipeline when config.assets.digest and
config.assets.compile are false and requested asset isn't precompiled.
Before the requested asset were compiled anyway ignoring that the
config.assets.compile flag is false. [Guillermo Iguaran]
* CookieJar is now Enumerable. Fixes #2795
* Fixed AssetNotPrecompiled error raised when rake assets:precompile
is compiling certain .erb files. See GH #2763 #2765 #2805 [Guillermo
Iguaran]
* Manifest is correctly placed in assets path when default assets
prefix is changed. Fixes #2776 [Guillermo Iguaran]
* Fixed stylesheet_link_tag and javascript_include_tag to respect
additional options passed by the users when debug is on. [Guillermo
Iguaran]
* Fix ActiveRecord#exists? when passsed a nil value
* Fix assert_select_email to work
[Rails-core] [ANN] Rails 3.1.1.rc3
Hi everyone,
Rails 3.1.1.rc3 has been released. Please give it a try, it's our
chance to fix regressions you might find and make a beautiful 3.1.1
stable release. If there are no regressions I will be releasing 3.1.1
final next October 7th. If you find any regression please contact me
ASAP by email, twitter or github.
## CHANGES
*ActionMailer*
* No changes
*ActionPack*
* stylesheet_link_tag('/stylesheets/application') and similar helpers doesn't
throw Sprockets::FileOutsidePaths exception anymore [Santiago Pastorino]
* Ensure default_asset_host_protocol is respected, closes #2980. [José Valim]
Changing rake db:schema:dump to run :environment as well as :load_config,
as running :load_config alone will lead to the dumper being run without
including extensions such as those included in foreigner and
spatial_adapter.
This reverses a change made here:
https://github.com/rails/rails/commit/5df72a238e9fcb18daf6ab6e6dc9051c9106d7bb#L0L324
I'm assuming here that :load_config needs to be invoked
separately from :environment, as it is elsewhere in the
file for db operations, if not the alternative is to go
back to task :dump = :environment do.
[Ben Woosley]
* Update to rack-cache 1.1.
Versions prior to 1.1 delete the If-Modified-Since and If-Not-Modified
headers when config.action_controller.perform_caching is true. This has two
problems:
* unexpected inconsistent behaviour between development
production environments
* breaks applications that use of these headers
[Brendan Ribera]
* Ensure that enhancements to assets:precompile task are only run once
[Sam Pohlenz]
* TestCase should respect the view_assigns API instead of pulling variables on
its own. [José Valim]
* javascript_path and stylesheet_path now refer to /assets if asset pipelining
is on. [Santiago Pastorino]
* button_to support form option. Now you're able to pass for example
'data-type' = 'json'. [ihower]
* image_path and image_tag should use /assets if asset pipelining is turned
on. Closes #3126 [Santiago Pastorino and christos]
* Avoid use of existing precompiled assets during rake assets:precompile run.
Closes #3119 [Guillermo Iguaran]
* Copy assets to nondigested filenames too [Santiago Pastorino]
* Give precedence to `config.digest = false` over the existence of
manifest.yml asset digests [christos]
* escape options for the stylesheet_link_tag method [Alexey Vakhov]
* Re-launch assets:precompile task using (Rake.)ruby instead of Kernel.exec so
it works on Windows [cablegram]
* env var passed to process shouldn't be modified in process method. [Santiago
Pastorino]
* `rake assets:precompile` loads the application but does not initialize
it.
To the app developer, this means configuration add in
config/initializers/* will not be executed.
Plugins developers need to special case their initializers that are
meant to be run in the assets group by adding :group = :assets. [José Valim]
* Sprockets uses config.assets.prefix for asset_path [asee]
* FileStore key_file_path properly limit filenames to 255 characters.
[phuibonhoa]
* Fix Hash#to_query edge case with html_safe strings. [brainopia]
* Allow asset tag helper methods to accept :digest = false option in
order to completely avoid the digest generation.
Useful for linking assets from static html files or from emails when the user
could probably look at an older html email with an older asset.
[Santiago Pastorino]
* Don't mount Sprockets server at config.assets.prefix if
config.assets.compile is false. [Mark J. Titorenko]
* Set relative url root in assets when controller isn't available for
Sprockets (eg. Sass files using asset_path). Fixes #2435 [Guillermo
Iguaran]
* Fix basic auth credential generation to not make newlines. GH #2882
* Fixed the behavior of asset pipeline when config.assets.digest and
config.assets.compile are false and requested asset isn't precompiled.
Before the requested asset were compiled anyway ignoring that the
config.assets.compile flag is false. [Guillermo Iguaran]
* CookieJar is now Enumerable. Fixes #2795
* Fixed AssetNotPrecompiled error raised when rake assets:precompile
is compiling certain .erb files. See GH #2763 #2765 #2805 [Guillermo
Iguaran]
* Manifest is correctly placed in assets path when default assets
prefix is changed. Fixes #2776 [Guillermo Iguaran]
* Fixed stylesheet_link_tag and javascript_include_tag to respect
additional options passed by the users when debug is on. [Guillermo
Iguaran]
* Fix ActiveRecord#exists? when passsed a nil value
* Fix assert_select_email to work on multipart and non-multipart
emails as the method stopped working correctly in Rails 3.x due to
changes in the new mail gem.
*ActiveModel*
* Remove hard dependency on bcrypt-ruby to avoid make ActiveModel
dependent on a binary library.
You must add the gem explicitly to your Gemfile if you want use
ActiveModel::SecurePassword:
gem 'bcrypt-ruby', '~ 3.0.0'
See GH #2687
Re: [Rails-core] sprockets 2.0.1 question (3.1.0 and 3.1.1.rc2)
You can still put assets in public/assets/ the thing is asset helper methods included from sprockets are not documented. This is confusing and we should fix it. On Sat, Oct 1, 2011 at 10:45 AM, Alexei Vakhov vak...@gmail.com wrote: Hello! I installed sprockets 2.0.1 and found that javascript_include_tag and stylesheet_link_tag dont' support script and style files from public folder anymore. If I use javascript_include_tag '/some-file-from-public.js' I get error that file not found in assets paths. Is it right behaviour? I prefer to use big 3rd party libraries like tinymce from public folder. In any case with new 2.0.1 version documentation pages http://api.rubyonrails.org/classes/ActionView/Helpers/AssetTagHelper/JavascriptTagHelpers.html#method-i-javascript_include_tag and http://api.rubyonrails.org/classes/ActionView/Helpers/AssetTagHelper/StylesheetTagHelpers.html#method-i-stylesheet_link_tag are obsoleted. Unfortunately I don't have time to investigate changes deep now :( -- Alexey Vakhov -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.1.1.rc2
Hi everyone, Rails 3.1.1.rc2 has been released. Please give it a try, it's our chance to fix regressions you might find and make a beautiful 3.1.1 stable release. If there are no regressions I will be releasing 3.1.1 final next October 3rd. If you find any regression please contact me ASAP by email, twitter or github. ## CHANGES *ActionMailer* * No changes *ActionPack* * Allow asset tag helper methods to accept :digest = false option in order to completely avoid the digest generation. Useful for linking assets from static html files or from emails when the user could probably look at an older html email with an older asset. [Santiago Pastorino] * Don't mount Sprockets server at config.assets.prefix if config.assets.compile is false. [Mark J. Titorenko] * Set relative url root in assets when controller isn't available for Sprockets (eg. Sass files using asset_path). Fixes #2435 [Guillermo Iguaran] * Fix basic auth credential generation to not make newlines. GH #2882 * Fixed the behavior of asset pipeline when config.assets.digest and config.assets.compile are false and requested asset isn't precompiled. Before the requested asset were compiled anyway ignoring that the config.assets.compile flag is false. [Guillermo Iguaran] * CookieJar is now Enumerable. Fixes #2795 * Fixed AssetNotPrecompiled error raised when rake assets:precompile is compiling certain .erb files. See GH #2763 #2765 #2805 [Guillermo Iguaran] * Manifest is correctly placed in assets path when default assets prefix is changed. Fixes #2776 [Guillermo Iguaran] * Fixed stylesheet_link_tag and javascript_include_tag to respect additional options passed by the users when debug is on. [Guillermo Iguaran] * Fix ActiveRecord#exists? when passsed a nil value * Fix assert_select_email to work on multipart and non-multipart emails as the method stopped working correctly in Rails 3.x due to changes in the new mail gem. *ActiveModel* * Remove hard dependency on bcrypt-ruby to avoid make ActiveModel dependent on a binary library. You must add the gem explicitly to your Gemfile if you want use ActiveModel::SecurePassword: gem 'bcrypt-ruby', '~ 3.0.0' See GH #2687. [Guillermo Iguaran] *ActiveRecord* * Add deprecation for the preload_associations method. Fixes #3022. [Jon Leighton] * Don't require a DB connection when loading a model that uses set_primary_key. GH #2807. [Jon Leighton] * Fix using select() with a habtm association, e.g. Person.friends.select(:name). GH #3030 and #2923. [Hendy Tanata] * Fix belongs_to polymorphic with custom primary key on target. GH #3104. [Jon Leighton] * CollectionProxy#replace should change the DB records rather than just mutating the array. Fixes #3020. [Jon Leighton] * LRU cache in mysql and sqlite are now per-process caches. * lib/active_record/connection_adapters/mysql_adapter.rb: LRU cache keys are per process id. * lib/active_record/connection_adapters/sqlite_adapter.rb: ditto * Database adapters use a statement pool for limiting the number of open prepared statments on the database. The limit defaults to 1000, but can be adjusted in your database config by changing 'statement_limit'. * Fix clash between using 'preload', 'joins' or 'eager_load' in a default scope and including the default scoped model in a nested through association. (GH #2834.) [Jon Leighton] * Ensure we are not comparing a string with a symbol in HasManyAssociation#inverse_updates_counter_cache?. Fixes GH #2755, where a counter cache could be decremented twice as far as it was supposed to be. [Jon Leighton] * Don't send any queries to the database when the foreign key of a belongs_to is nil. Fixes GH #2828. [Georg Friedrich] * Fixed find_in_batches method to not include order from default_scope. See GH #2832 [Arun Agrawal] * Don't compute table name for abstract classes. Fixes problem with setting the primary key in an abstract class. See GH #2791. [Akira Matsuda] * Psych errors with poor yaml formatting are proxied. Fixes GH #2645 and GH #2731 * Use the LIMIT word with the methods #last and #first. Fixes GH #2783 [Damien Mathieu] *ActiveResource* * No changes *ActiveSupport* * Fixed performance issue where TimeZone lookups would require tzinfo each time [Tim Lucas] * ActiveSupport::OrderedHash is now marked as extractable when using Array#extract_options! [Prem Sichanugrist] *Railties* * Add jquery-rails to Gemfile of plugins, test/dummy app needs it. Closes #3091. [Santiago Pastorino] * `rake assets:precompile` loads the application but does not initialize it. To the app developer, this means configuration add in config/initializers/* will not be executed. Plugins developers need to special case their initializers that are meant to be run in the assets group by adding :group = :assets. You can find an exhaustive list of changes on [github](https://github.com/rails/rails/compare/v3.1.0...v3.1.1.rc2). Along
Re: [Rails-core] rails 3.1.1
We are about to go, just waiting for this https://github.com/rails/sass-rails/issues/57 to be fixed. On Tue, Sep 27, 2011 at 11:29 AM, Corin Langosch corin.lango...@netskin.com wrote: Hi there, I'd just like to ask if rails 3.1.1 (announced to be released 16th September) will ever be released or will 3.1.2 the next release? According to github there are no remaining issues for 3.1.1. Thanks, Corin -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.1.1.rc1
Hi everyone, Rails 3.1.1.rc1 has been released. Please give it a try, it's our chance to fix regressions you might find and make a beautiful 3.1.1 stable release. If there are no regressions I will be releasing 3.1.1 final next September 16th during GoGaRuCo. ## CHANGES *ActionMailer* * No changes *ActionPack* * Allow asset tag helper methods to accept :digest = false option in order to completely avoid the digest generation. Useful for linking assets from static html files or from emails when the user could probably look at an older html email with an older asset. [Santiago Pastorino] * Don't mount Sprockets server at config.assets.prefix if config.assets.compile is false. [Mark J. Titorenko] * Set relative url root in assets when controller isn't available for Sprockets (eg. Sass files using asset_path). Fixes #2435 [Guillermo Iguaran] * Fix basic auth credential generation to not make newlines. GH #2882 * Fixed the behavior of asset pipeline when config.assets.digest and config.assets.compile are false and requested asset isn't precompiled. Before the requested asset were compiled anyway ignoring that the config.assets.compile flag is false. [Guillermo Iguaran] * CookieJar is now Enumerable. Fixes #2795 * Fixed AssetNotPrecompiled error raised when rake assets:precompile is compiling certain .erb files. See GH #2763 #2765 #2805 [Guillermo Iguaran] * Manifest is correctly placed in assets path when default assets prefix is changed. Fixes #2776 [Guillermo Iguaran] * Fixed stylesheet_link_tag and javascript_include_tag to respect additional options passed by the users when debug is on. [Guillermo Iguaran] * Fix ActiveRecord#exists? when passsed a nil value * Fix assert_select_email to work on multipart and non-multipart emails as the method stopped working correctly in Rails 3.x due to changes in the new mail gem. *ActiveModel* * Remove hard dependency on bcrypt-ruby to avoid make ActiveModel dependent on a binary library. You must add the gem explicitly to your Gemfile if you want use ActiveModel::SecurePassword: gem 'bcrypt-ruby', '~ 3.0.0' See GH #2687. [Guillermo Iguaran] *ActiveRecord* * LRU cache in mysql and sqlite are now per-process caches. * lib/active_record/connection_adapters/mysql_adapter.rb: LRU cache keys are per process id. * lib/active_record/connection_adapters/sqlite_adapter.rb: ditto * Database adapters use a statement pool for limiting the number of open prepared statments on the database. The limit defaults to 1000, but can be adjusted in your database config by changing 'statement_limit'. * Fix clash between using 'preload', 'joins' or 'eager_load' in a default scope and including the default scoped model in a nested through association. (GH #2834.) [Jon Leighton] * Ensure we are not comparing a string with a symbol in HasManyAssociation#inverse_updates_counter_cache?. Fixes GH #2755, where a counter cache could be decremented twice as far as it was supposed to be. [Jon Leighton] * Don't send any queries to the database when the foreign key of a belongs_to is nil. Fixes GH #2828. [Georg Friedrich] * Fixed find_in_batches method to not include order from default_scope. See GH #2832 [Arun Agrawal] * Don't compute table name for abstract classes. Fixes problem with setting the primary key in an abstract class. See GH #2791. [Akira Matsuda] * Psych errors with poor yaml formatting are proxied. Fixes GH #2645 and GH #2731 * Use the LIMIT word with the methods #last and #first. Fixes GH #2783 [Damien Mathieu] *ActiveResource* * No changes *ActiveSupport* * Fixed performance issue where TimeZone lookups would require tzinfo each time [Tim Lucas] * ActiveSupport::OrderedHash is now marked as extractable when using Array#extract_options! [Prem Sichanugrist] *Railties* * No changes You can find an exhaustive list of changes on [github](https://github.com/rails/rails/compare/v3.1.0...v3.1.1.rc1). Along with the [closed issues marked for v3.1.1](https://github.com/rails/rails/issues?milestone=6state=closed). You can also see issues [we haven't closed yet](https://github.com/rails/rails/issues?milestone=8state=open). Thanks to everyone! -- Twitter: http://twitter.com/spastorino Github: http://github.com/spastorino -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.1.0.rc8
Hi everyone, Rails 3.1.0.rc8 has been released (we've an issue with rc7). This is the final release candidate. Please give it a try, it's our last chance to fix regressions and severe issues. We will be releasing final 3.1.0 next August 30th. ## CHANGES Check the CHANGELOG file of each framework to see what we've changed. You can find an exhaustive list of changes on [github](https://github.com/rails/rails/compare/v3.1.0.rc6...v3.1.0.rc8). Along with the [closed issues marked for v3.1.0](https://github.com/rails/rails/issues?sort=createddirection=descstate=closedpage=1milestone=1). You can also see issues [we haven't closed](https://github.com/rails/rails/issues?sort=createddirection=descstate=openpage=1milestone=1). A comprehensive CHANGELOG will be announced when 3.1.0 final is released. Thanks! -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Rails 3.1.0.rc5
Aaron, in the case of 3.1 I'd say please test using 3-1-stable. To do this replace you gem 'rails' entry with the following in the Gemfile gem 'rails', :git = 'git://github.com/rails/rails.git', :branch = '3-1-stable' There are a lot of issues already fixed there, and we don't want duplicated reports ;). Cheers. On Thu, Aug 11, 2011 at 8:44 PM, Aaron Patterson aa...@tenderlovemaking.com wrote: Please continue to test 3.0.10.rc1, and 3.1.0.rc5. Let us know about -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] rails 3.1rc4, Engine rather broken
Can you please confirm and fill this issues in a bug report?. With the latest edge code I don't get that ... ➜ /tmp ruby ~/WyeWorks/Projs/rails/bin/rails new myengine --mountable --dev create create README create Rakefile create config.ru create .gitignore create Gemfile create app create app/assets/images/rails.png create app/assets/javascripts/application.js create app/assets/stylesheets/application.css create app/controllers/application_controller.rb create app/helpers/application_helper.rb create app/mailers create app/models create app/views/layouts/application.html.erb create app/mailers/.gitkeep create app/models/.gitkeep create config create config/routes.rb create config/application.rb create config/environment.rb create config/environments create config/environments/development.rb create config/environments/production.rb create config/environments/test.rb create config/initializers create config/initializers/backtrace_silencers.rb create config/initializers/inflections.rb create config/initializers/mime_types.rb create config/initializers/secret_token.rb create config/initializers/session_store.rb create config/initializers/wrap_parameters.rb create config/locales create config/locales/en.yml create config/boot.rb create config/database.yml create db create db/seeds.rb create doc create doc/README_FOR_APP create lib create lib/tasks create lib/tasks/.gitkeep create lib/assets create lib/assets/.gitkeep create log create log/.gitkeep create public create public/404.html create public/422.html create public/500.html create public/favicon.ico create public/index.html create public/robots.txt create script create script/rails create test/fixtures create test/fixtures/.gitkeep create test/functional create test/functional/.gitkeep create test/integration create test/integration/.gitkeep create test/unit create test/unit/.gitkeep create test/performance/browsing_test.rb create test/test_helper.rb create tmp/cache create tmp/cache/.gitkeep create vendor/assets/stylesheets create vendor/assets/stylesheets/.gitkeep create vendor/plugins create vendor/plugins/.gitkeep run bundle install Updating git://github.com/rails/sass-rails Updating git://github.com/rails/coffee-rails Fetching source index for http://rubygems.org/ Using rake (0.9.2) Using i18n (0.6.0) Using multi_json (1.0.3) Using activesupport (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using bcrypt-ruby (2.1.4) Using builder (3.0.0) Using activemodel (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using erubis (2.7.0) Using rack (1.3.0) Using rack-cache (1.0.2) Using rack-mount (0.8.1) Using rack-test (0.6.0) Using hike (1.1.0) Using tilt (1.3.2) Using sprockets (2.0.0.beta.10) Using tzinfo (0.3.29) Using actionpack (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using mime-types (1.16) Using polyglot (0.3.1) Using treetop (1.4.9) Using mail (2.3.0) Using actionmailer (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using arel (2.1.3) Using activerecord (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using activeresource (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using ansi (1.3.0) Using bundler (1.0.15) Using coffee-script-source (1.1.1) Using execjs (1.2.0) Using coffee-script (2.2.0) Using rack-ssl (1.3.2) Using rdoc (3.8) Using thor (0.14.6) Using railties (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using coffee-rails (3.2.0.beta) from git://github.com/rails/coffee-rails (at master) Using jquery-rails (1.0.12) Using rails (3.2.0.beta) from source at /Users/santiago/WyeWorks/Projs/rails Using sass (3.1.4) Using sass-rails (3.1.1.alpha.0) from git://github.com/rails/sass-rails (at master) Using sqlite3 (1.3.3) Using turn (0.8.2) Using uglifier (1.0.0) Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed. ➜ /tmp cd myengine ➜ myengine rails g scaffold post invoke active_record createdb/migrate/20110707161601_create_posts.rb createapp/models/post.rb invoketest_unit create test/unit/post_test.rb create test/fixtures/posts.yml route resources :posts invoke scaffold_controller createapp/controllers/posts_controller.rb invokeerb create app/views/posts create app/views/posts/index.html.erb create app/views/posts/edit.html.erb create
[Rails-core] [ANN] Rails 3.0.7.rc2
ZOMG I've pushed 3.0.7.rc2 to rubygems. Please read the announcement for 3.0.7.rc1: http://groups.google.com/group/rubyonrails-core/browse_thread/thread/c9267eb6a47f8505 Here are the changes between 3.0.7.rc1 and 3.0.7.rc2: https://github.com/rails/rails/compare/v3.0.7.rc1...v3.0.7.rc2 Aaron is going to release 3.0.7 final for at least 72 hours from now, because I will be on vacations. So I guess Monday (PDT) we will have the final release. Again, please let us know (on the rails core mailing list) if any changes we've made between 3.0.6 and 3.0.7.rc2 break your application! Thanks!!!. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] [ANN] Rails 3.0.7.rc1
Great guys, thanks for testing the rc with your apps. You can test now rc2 just in case :). On Fri, Apr 15, 2011 at 5:28 AM, Tekin Suleyman te...@tekin.co.uk wrote: We are asking you (yes you!) to *try out* the release candidate. If something that changed between 3.0.6 and this release candidate breaks your application, we want to know about it! All green here too. Tekin Suleyman -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] [ANN] Rails 3.0.7.rc1
I'm happy to announce that Rails 3.0.7.rc1 has been pushed to rubygems. ## Release Candidate: What does it mean? The release candidate is very similar to what we will actually release for version 3.0.7. The reason that we release an RC is so that the community can have a chance to postpone or veto commits that have happened between the previous version and the version we're about to release. We are asking you (yes you!) to *try out* the release candidate. If something that changed between 3.0.6 and this release candidate breaks your application, we want to know about it! ## How do I try it out? Simply update your Gemfile to point at the rails version 3.0.7.rc1, then `bundle install`. ## Where can I see a list of Changes? Either look at the CHANGELOG in each particular project on [github](https://github.com/rails/rails/tree/3-0-7), *or* check out the handy [compare view](https://github.com/rails/rails/compare/v3.0.6…v3.0.7.rc1). Again, per project changelogs: https://github.com/rails/rails/tree/3-0-7 *or* compare view: https://github.com/rails/rails/compare/v3.0.6...v3.0.7.rc1 ## Something is broken, what should I do? Email the [rails core mailing list](http://groups.google.com/group/rubyonrails-core) at let us know about the problem! We will discuss the problem and how to handle it before the final version is pushed. ## When will the final version be released? Unless there are problems found in the RC, we will release the final version no less than 72 hours from *now*. If there are problems found in the RC, we will release another RC and give the community another chance to test before releasing. ## In closing Remember, this is *your* chance to veto / postpone our release. Please take advantage of this opportunity! We do not want to break people's applications. The best we can do is ask for help! Thanks to everyone. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] [ANN] Rails 3.0.7.rc1
Just in case here you are again ... https://github.com/rails/rails/compare/v3.0.6...v3.0.7.rc1 On Thu, Apr 14, 2011 at 8:37 PM, Ryan Bigg radarliste...@gmail.com wrote: All green here too! I couldn't get the GitHub compare view to work though... is the URL wrong? -- Ryan Bigg On Friday, 15 April 2011 at 9:32 AM, Nicolás Sanguinetti wrote: And actually, `bundle update rails`. You don't want bundler updating all the gems :) On Thu, Apr 14, 2011 at 8:23 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Em 14-04-2011 19:03, Santiago Pastorino escreveu: ...Simply update your Gemfile to point at the rails version 3.0.7.rc1, then `bundle install`. Actually, 'bundle update'... :) All my specs are passing green :) Regards, Rodrigo. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: rails_upgrade plugin needs your help too
Great Everton! On Tue, Mar 1, 2011 at 12:01 PM, Everton Moreth everton.mor...@gmail.com wrote: I just got an answer, he will still maintain it, and Ill send any updates I make. Thanks! EMoreth On Tue, Mar 1, 2011 at 10:49 AM, Everton Moreth everton.mor...@gmail.com wrote: I sent him another message on github. Ill start working on that, and then we see what we do. Regards, EMoreth On Fri, Feb 25, 2011 at 4:33 PM, Everton Moreth everton.mor...@gmail.com wrote: On Wed, Feb 23, 2011 at 9:15 AM, Santiago Pastorino santi...@wyeworks.com wrote: No sorry :(, message him through github or twitter. I guess he is very busy. I will try to ask him again. Cheers. On Wed, Feb 23, 2011 at 10:09 AM, Everton Moreth everton.mor...@gmail.com wrote: Any news? I'm pretty excited about this. EMoreth Em 19/02/2011 13:40, Santiago Pastorino santi...@wyeworks.comescreveu: I have sent him a message. On Fri, Feb 18, 2011 at 6:05 PM, EMoreth everton.mor...@gmail.com wrote: Still no answer... ... -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. Any news?? EMoreth -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] Re: Rails plugins new official maintainers
All the https://github.com/rails plugins now point to the ones listed in my previous email. Please let me know about any errors or if someone needs access. Cheers. On Fri, Feb 18, 2011 at 5:26 PM, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, This is the final list of the new maintainers of each plugin. We need two more things to do: First please the owners of the repos add the rest of the maintainers. Second I will add a note on each rails/plugin mentioning this repos updates. So from now on, if someone else is interested in helping/contributing please send a message to the appropriate repo owner. verification (https://github.com/sikachu/verification) Prem Sichanugrist Rishav Rastogi country_select (https://github.com/chrislerum/country_select) Mark Turner Chris Lerum Devdatta dynamic_form (https://github.com/joelmoss/dynamic_form) Prem Sichanugrist Joel Moss Devdatta exception_notification (https://github.com/smartinez87/exception_notification) Sebastián Martínez Jason King Devdatta acts_as_list (https://github.com/swanandp/acts_as_list) Mark Turner Swanand Pagnis hide_action (https://github.com/sikachu/hide_action) Prem Sichanugrist open_id_authentication (https://github.com/Velir/open_id_authentication) Anuj Dutta Patrick Robertson asset_server (https://github.com/andhapp/asset_server) Anuj Dutta Rishav Rastogi in_place_editing (https://github.com/amerine/in_place_editing) Mark Turner Devdatta upload_progress (https://github.com/rishav/upload_progress) Rishav Rastogi token_generator (https://github.com/bbommarito/token_generator) BrianBommarito ssl_requirement (https://github.com/retr0h/ssl_requirement) Lars Smit John Dewey Steven Soroka scaffolding (https://github.com/KeysetTS/scaffolding) Brandon http_authentication (https://github.com/dshimy/http_authentication) Darian Shimy Lars Smit auto_complete (https://github.com/david-kerins/auto_complete) dkerins Devdatta atom_feed_helper (https://github.com/TrevorBramble/atom_feed_helper) Trevor Bramble acts_as_tree (https://github.com/amerine/acts_as_tree) Mark Turner Swanand Pagnis acts_as_nested_set (https://github.com/bbommarito/acts_as_nested_set) BrianBommarito account_location (https://github.com/bbommarito/account_location) BrianBommarito render_component (https://github.com/malev/render_component) Marcos Vanetta localization (https://github.com/malev/localization) Marcos Vanetta deadlock_retry (https://github.com/heaps/deadlock_retry) Kieran P And no body is interested in ... prototype_legacy_helper fcgi_handler sqlite2_adapter irs_process_scripts request_profiler render_component deadlock_retry iso-3166-country-select tzinfo_timezone tztime scriptaculous_slider javascript_test continuous_builder So they are not maintained anymore. Cheers, Santiago. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: rails_upgrade plugin needs your help too
I have sent him a message. On Fri, Feb 18, 2011 at 6:05 PM, EMoreth everton.mor...@gmail.com wrote: Still no answer... Can u help me with that ? EMoreth On Feb 18, 8:41 am, EMoreth everton.mor...@gmail.com wrote: I did that yesterday. Waiting for his answer. EMoreth On Feb 18, 12:41 am, Santiago Pastorino santi...@wyeworks.com wrote: Hey Everton, Peer, Please ping Jeremy on github and if he didn't reply let me know and I will try to reach him. I was talking with him today and he was very pleased to be helped on rails_upgrade. Thanks guys, Santiago. On Thu, Feb 17, 2011 at 9:44 PM, Peer Allan pal...@allanweb.ca wrote: I just sent a message to Jeremy offering help. I have several updates to the plugin that i have been waiting to be pulled in. Thanks for the notice, Santiago. Peer On Thu, Feb 17, 2011 at 5:30 PM, EMoreth everton.mor...@gmail.com wrote: I was asking for this! I have at least 9 rails 2.3.8 projects that need to upgrade as soon as possible! I already asked him for continue maintenance, but I got no answer. Ill send another github message. Everton On Feb 17, 8:37 pm, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, Jeremy McAnally is asking for help onhttps://github.com/jm/rails_upgradeplugin, please contact him preferably on github (http://github.com/jm). I remember some guys asked about rails_upgrade, so now you know just go ahead and ping Jeremy on github or twitter. Cheers, Santiago. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Maintainers of Rails plugins
Joel, can we set https://github.com/joelmoss/dynamic_form as the official one? Thanks. On Fri, Feb 18, 2011 at 8:19 AM, Joel Moss j...@developwithstyle.com wrote: Doh! What I meant to say was The one on Github is not kept up to date, but the Codaset one is. ;) -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:00, Joel Moss wrote: The repo I use is actually at Codaset http://codaset.com/joelmoss/dynamic-form. The one on Codaest is not kept up to date, but the Codaset one is. thx -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 09:19, Prem Sichanugrist wrote: Santago, can you make Joel Moss repository as the main one? He's already maintaining it, why I've done nothing to it. https://github.com/joelmoss/dynamic_form Sent from my iPhone On 18 ก.พ. 2554, at 5:31, Sebastian Martinez smartine...@gmail.com wrote: Hi guys, I've added Jason King (https://github.com/JasonKing) and Devdatta (https://github.com/devdatta) to the exception_notification repository (https://github.com/smartinez87/exception_notification) Thanks Santiago for putting all this together. Cheers, Sebastian On Feb 17, 8:05 pm, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, As you probably know Rails needs lot of help in some fronts and the resources we have are just a few. So besides calling for people to contribute to Rails itself, we are asking for help to maintain most of the plugins we have onhttps://github.com/rails We made a call some days ago and these are the results. Please take a look below and verify that everything is ok. I still need some URLs to the repos and also that the owners give commit access to the fellow maintainers. verification ( please send me the address of the repo ) Prem Sichanugrist Rishav Rastogi country_select (https://github.com/chrislerum/country_select) Mark Turner Chris Lerum Devdatta dynamic_form ( please send me the address of the repo ) Prem Sichanugrist Joel Moss Devdatta exception_notification (https://github.com/smartinez87/exception_notification) Sebastián Martínez Jason King Devdatta acts_as_list (https://github.com/swanandp/acts_as_list) Mark Turner Swanand Pagnis hide_action ( please send me the address of the repo ) Prem Sichanugrist open_id_authentication (https://github.com/Velir/open_id_authentication) Anuj Dutta Patrick Robertson asset_server (https://github.com/andhapp/asset_server) Anuj Dutta Rishav Rastogi in_place_editing (https://github.com/amerine/in_place_editing) Mark Turner Devdatta upload_progress Rishav Rastogi token_generator (https://github.com/bbommarito/token_generator) BrianBommarito ssl_requirement (https://github.com/retr0h/ssl_requirement) Lars Smit John Dewey Steven Soroka scaffolding (https://github.com/KeysetTS/scaffolding) Brandon http_authentication (https://github.com/dshimy/http_authentication) Darian Shimy Lars Smit auto_complete (https://github.com/david-kerins/auto_complete) dkerins Devdatta atom_feed_helper (https://github.com/TrevorBramble/atom_feed_helper) Trevor Bramble acts_as_tree (https://github.com/amerine/acts_as_tree) Mark Turner Swanand Pagnis acts_as_nested_set (https://github.com/bbommarito/acts_as_nested_set) BrianBommarito account_location (https://github.com/bbommarito/account_location) BrianBommarito And no body is interested in ... prototype_legacy_helper fcgi_handler sqlite2_adapter irs_process_scripts request_profiler render_component deadlock_retry iso-3166-country-select tzinfo_timezone tztime scriptaculous_slider localization javascript_test continuous_builder So they are not maintained anymore. Cheers, Santiago. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received
Re: [Rails-core] Re: Maintainers of Rails plugins
Hehe Joel I can tell that is very cool yeah ;). OK thanks :). On Fri, Feb 18, 2011 at 12:17 PM, Joel Moss j...@developwithstyle.com wrote: Well of course Codaset is awesome! ;) Ok, no problem. I'll update the Github repo. -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 13:55, Santiago Pastorino wrote: Joel, Even though Codaset is awesome, the preferred way at the moment for rails and the plugins we have under ours scope is github. So please if we can use your github as the official repo for dynamic_form that would be great. Thanks and sorry about that. On Fri, Feb 18, 2011 at 8:54 AM, Joel Moss j...@developwithstyle.com wrote: I would prefer to use the one at Codaset, as that is what I use. If that's a problem, please let me know. -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:45, Santiago Pastorino wrote: Joel, can we set https://github.com/joelmoss/dynamic_form as the official one? Thanks. On Fri, Feb 18, 2011 at 8:19 AM, Joel Moss j...@developwithstyle.com wrote: Doh! What I meant to say was The one on Github is not kept up to date, but the Codaset one is. ;) -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:00, Joel Moss wrote: The repo I use is actually at Codaset http://codaset.com/joelmoss/dynamic-form. The one on Codaest is not kept up to date, but the Codaset one is. thx -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 09:19, Prem Sichanugrist wrote: Santago, can you make Joel Moss repository as the main one? He's already maintaining it, why I've done nothing to it. https://github.com/joelmoss/dynamic_form Sent from my iPhone On 18 ก.พ. 2554, at 5:31, Sebastian Martinez smartine...@gmail.com wrote: Hi guys, I've added Jason King (https://github.com/JasonKing) and Devdatta (https://github.com/devdatta) to the exception_notification repository (https://github.com/smartinez87/exception_notification) Thanks Santiago for putting all this together. Cheers, Sebastian On Feb 17, 8:05 pm, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, As you probably know Rails needs lot of help in some fronts and the resources we have are just a few. So besides calling for people to contribute to Rails itself, we are asking for help to maintain most of the plugins we have onhttps://github.com/rails We made a call some days ago and these are the results. Please take a look below and verify that everything is ok. I still need some URLs to the repos and also that the owners give commit access to the fellow maintainers. verification ( please send me the address of the repo ) Prem Sichanugrist Rishav Rastogi country_select (https://github.com/chrislerum/country_select) Mark Turner Chris Lerum Devdatta dynamic_form ( please send me the address of the repo ) Prem Sichanugrist Joel Moss Devdatta exception_notification (https://github.com/smartinez87/exception_notification) Sebastián Martínez Jason King Devdatta acts_as_list (https://github.com/swanandp/acts_as_list) Mark Turner Swanand Pagnis hide_action ( please send me the address of the repo ) Prem Sichanugrist open_id_authentication (https://github.com/Velir/open_id_authentication) Anuj Dutta Patrick Robertson asset_server (https://github.com/andhapp/asset_server) Anuj Dutta Rishav Rastogi in_place_editing (https://github.com/amerine/in_place_editing) Mark Turner Devdatta upload_progress Rishav Rastogi token_generator (https://github.com/bbommarito/token_generator) BrianBommarito ssl_requirement (https://github.com/retr0h/ssl_requirement) Lars Smit John Dewey Steven Soroka scaffolding (https://github.com/KeysetTS/scaffolding) Brandon http_authentication (https://github.com/dshimy/http_authentication) Darian Shimy Lars Smit auto_complete (https://github.com/david-kerins/auto_complete) dkerins Devdatta atom_feed_helper (https://github.com/TrevorBramble/atom_feed_helper
Re: [Rails-core] Re: Maintainers of Rails plugins
Joel, yes go ahead our suggestion is to give access too to the other interested guys. Thanks. On Fri, Feb 18, 2011 at 12:22 PM, Joel Moss j...@developwithstyle.com wrote: All done and updated: https://github.com/joelmoss/dynamic_form What do you want to do about the project on RubyGems.org. I control that too. Shall I keep it as it is and control releases myself? -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 14:17, Joel Moss wrote: Well of course Codaset is awesome! ;) Ok, no problem. I'll update the Github repo. -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 13:55, Santiago Pastorino wrote: Joel, Even though Codaset is awesome, the preferred way at the moment for rails and the plugins we have under ours scope is github. So please if we can use your github as the official repo for dynamic_form that would be great. Thanks and sorry about that. On Fri, Feb 18, 2011 at 8:54 AM, Joel Moss j...@developwithstyle.com wrote: I would prefer to use the one at Codaset, as that is what I use. If that's a problem, please let me know. -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:45, Santiago Pastorino wrote: Joel, can we set https://github.com/joelmoss/dynamic_form as the official one? Thanks. On Fri, Feb 18, 2011 at 8:19 AM, Joel Moss j...@developwithstyle.com wrote: Doh! What I meant to say was The one on Github is not kept up to date, but the Codaset one is. ;) -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:00, Joel Moss wrote: The repo I use is actually at Codaset http://codaset.com/joelmoss/dynamic-form. The one on Codaest is not kept up to date, but the Codaset one is. thx -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 09:19, Prem Sichanugrist wrote: Santago, can you make Joel Moss repository as the main one? He's already maintaining it, why I've done nothing to it. https://github.com/joelmoss/dynamic_form Sent from my iPhone On 18 ก.พ. 2554, at 5:31, Sebastian Martinez smartine...@gmail.com wrote: Hi guys, I've added Jason King (https://github.com/JasonKing) and Devdatta (https://github.com/devdatta) to the exception_notification repository (https://github.com/smartinez87/exception_notification) Thanks Santiago for putting all this together. Cheers, Sebastian On Feb 17, 8:05 pm, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, As you probably know Rails needs lot of help in some fronts and the resources we have are just a few. So besides calling for people to contribute to Rails itself, we are asking for help to maintain most of the plugins we have onhttps://github.com/rails We made a call some days ago and these are the results. Please take a look below and verify that everything is ok. I still need some URLs to the repos and also that the owners give commit access to the fellow maintainers. verification ( please send me the address of the repo ) Prem Sichanugrist Rishav Rastogi country_select (https://github.com/chrislerum/country_select) Mark Turner Chris Lerum Devdatta dynamic_form ( please send me the address of the repo ) Prem Sichanugrist Joel Moss Devdatta exception_notification (https://github.com/smartinez87/exception_notification) Sebastián Martínez Jason King Devdatta acts_as_list (https://github.com/swanandp/acts_as_list) Mark Turner Swanand Pagnis hide_action ( please send me the address of the repo ) Prem Sichanugrist open_id_authentication (https://github.com/Velir/open_id_authentication) Anuj Dutta Patrick Robertson asset_server (https://github.com/andhapp/asset_server) Anuj Dutta Rishav Rastogi in_place_editing (https://github.com/amerine
Re: [Rails-core] Re: Maintainers of Rails plugins
Joel the idea is that the official repo for dynamic_form is now https://github.com/joelmoss/dynamic_form with you, Prem Sichanugrist and Devdatta as maintainers. I will update the rails/dynamic_form info with a note saying that and pointing to yours. On Fri, Feb 18, 2011 at 12:29 PM, Joel Moss j...@developwithstyle.com wrote: And who shall we issue pull requests to for the official repo at github/rails/dynamic_form? -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 14:25, Santiago Pastorino wrote: Joel, yes go ahead our suggestion is to give access too to the other interested guys. Thanks. On Fri, Feb 18, 2011 at 12:22 PM, Joel Moss j...@developwithstyle.com wrote: All done and updated: https://github.com/joelmoss/dynamic_form What do you want to do about the project on RubyGems.org. I control that too. Shall I keep it as it is and control releases myself? -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 14:17, Joel Moss wrote: Well of course Codaset is awesome! ;) Ok, no problem. I'll update the Github repo. -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 13:55, Santiago Pastorino wrote: Joel, Even though Codaset is awesome, the preferred way at the moment for rails and the plugins we have under ours scope is github. So please if we can use your github as the official repo for dynamic_form that would be great. Thanks and sorry about that. On Fri, Feb 18, 2011 at 8:54 AM, Joel Moss j...@developwithstyle.com wrote: I would prefer to use the one at Codaset, as that is what I use. If that's a problem, please let me know. -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:45, Santiago Pastorino wrote: Joel, can we set https://github.com/joelmoss/dynamic_form as the official one? Thanks. On Fri, Feb 18, 2011 at 8:19 AM, Joel Moss j...@developwithstyle.com wrote: Doh! What I meant to say was The one on Github is not kept up to date, but the Codaset one is. ;) -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 10:00, Joel Moss wrote: The repo I use is actually at Codaset http://codaset.com/joelmoss/dynamic-form. The one on Codaest is not kept up to date, but the Codaset one is. thx -- Joel Moss Develop with Style at http://DevelopWithStyle.com Really useful software project management: http://Codaset.com === Call me +44 7791 503309 http://twitter.com/joelmoss AIM: joelkmoss MSIM: j...@joelmoss.info Skype: joelmoss.info On Friday, 18 February 2011 at 09:19, Prem Sichanugrist wrote: Santago, can you make Joel Moss repository as the main one? He's already maintaining it, why I've done nothing to it. https://github.com/joelmoss/dynamic_form Sent from my iPhone On 18 ก.พ. 2554, at 5:31, Sebastian Martinez smartine...@gmail.com wrote: Hi guys, I've added Jason King (https://github.com/JasonKing) and Devdatta (https://github.com/devdatta) to the exception_notification repository (https://github.com/smartinez87/exception_notification) Thanks Santiago for putting all this together. Cheers, Sebastian On Feb 17, 8:05 pm, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, As you probably know Rails needs lot of help in some fronts and the resources we have are just a few. So besides calling for people to contribute to Rails itself, we are asking for help to maintain most of the plugins we have onhttps://github.com/rails We made a call some days ago and these are the results. Please take a look below and verify that everything is ok. I still need some URLs to the repos and also that the owners give commit access to the fellow maintainers. verification ( please send me
[Rails-core] Maintainers of Rails plugins
Hey guys, As you probably know Rails needs lot of help in some fronts and the resources we have are just a few. So besides calling for people to contribute to Rails itself, we are asking for help to maintain most of the plugins we have on https://github.com/rails We made a call some days ago and these are the results. Please take a look below and verify that everything is ok. I still need some URLs to the repos and also that the owners give commit access to the fellow maintainers. verification ( please send me the address of the repo ) Prem Sichanugrist Rishav Rastogi country_select (https://github.com/chrislerum/country_select) Mark Turner Chris Lerum Devdatta dynamic_form ( please send me the address of the repo ) Prem Sichanugrist Joel Moss Devdatta exception_notification (https://github.com/smartinez87/exception_notification) Sebastián Martínez Jason King Devdatta acts_as_list (https://github.com/swanandp/acts_as_list) Mark Turner Swanand Pagnis hide_action ( please send me the address of the repo ) Prem Sichanugrist open_id_authentication (https://github.com/Velir/open_id_authentication) Anuj Dutta Patrick Robertson asset_server (https://github.com/andhapp/asset_server) Anuj Dutta Rishav Rastogi in_place_editing (https://github.com/amerine/in_place_editing) Mark Turner Devdatta upload_progress Rishav Rastogi token_generator (https://github.com/bbommarito/token_generator) BrianBommarito ssl_requirement (https://github.com/retr0h/ssl_requirement) Lars Smit John Dewey Steven Soroka scaffolding (https://github.com/KeysetTS/scaffolding) Brandon http_authentication (https://github.com/dshimy/http_authentication) Darian Shimy Lars Smit auto_complete (https://github.com/david-kerins/auto_complete) dkerins Devdatta atom_feed_helper (https://github.com/TrevorBramble/atom_feed_helper) Trevor Bramble acts_as_tree (https://github.com/amerine/acts_as_tree) Mark Turner Swanand Pagnis acts_as_nested_set (https://github.com/bbommarito/acts_as_nested_set) BrianBommarito account_location (https://github.com/bbommarito/account_location) BrianBommarito And no body is interested in ... prototype_legacy_helper fcgi_handler sqlite2_adapter irs_process_scripts request_profiler render_component deadlock_retry iso-3166-country-select tzinfo_timezone tztime scriptaculous_slider localization javascript_test continuous_builder So they are not maintained anymore. Cheers, Santiago. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] rails_upgrade plugin needs your help too
Hey guys, Jeremy McAnally is asking for help on https://github.com/jm/rails_upgrade plugin, please contact him preferably on github (http://github.com/jm). I remember some guys asked about rails_upgrade, so now you know just go ahead and ping Jeremy on github or twitter. Cheers, Santiago. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: rails_upgrade plugin needs your help too
Hey Everton, Peer, Please ping Jeremy on github and if he didn't reply let me know and I will try to reach him. I was talking with him today and he was very pleased to be helped on rails_upgrade. Thanks guys, Santiago. On Thu, Feb 17, 2011 at 9:44 PM, Peer Allan pal...@allanweb.ca wrote: I just sent a message to Jeremy offering help. I have several updates to the plugin that i have been waiting to be pulled in. Thanks for the notice, Santiago. Peer On Thu, Feb 17, 2011 at 5:30 PM, EMoreth everton.mor...@gmail.com wrote: I was asking for this! I have at least 9 rails 2.3.8 projects that need to upgrade as soon as possible! I already asked him for continue maintenance, but I got no answer. Ill send another github message. Everton On Feb 17, 8:37 pm, Santiago Pastorino santi...@wyeworks.com wrote: Hey guys, Jeremy McAnally is asking for help onhttps://github.com/jm/rails_upgradeplugin, please contact him preferably on github (http://github.com/jm). I remember some guys asked about rails_upgrade, so now you know just go ahead and ping Jeremy on github or twitter. Cheers, Santiago. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
Hey guys, yeah I will post the list of repositories and maintainers ASAP, sorry about the delay, too much work here :(. Cheers, Santiago. On Tue, Feb 15, 2011 at 2:53 PM, david-kerins bitbox...@gmail.com wrote: Santiago, are you still going to follow up on this. I haven't heard from you so maybe you don't need me as a maintainer. Please let me know. Thanks. David On Feb 1, 8:04 pm, Santiago Pastorino santi...@wyeworks.com wrote: We are looking for maintainers for the rails plugins listed inhttp://github.com/railsexcept arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] A patch for tricky joins causing table name collisions
Pushed to master, thanks.
On Sat, Feb 12, 2011 at 5:30 PM, Ernie Miller er...@metautonomo.us wrote:
In master, there's a regression in the new association handling cod. Way back
in a patch I submitted to 3.0 to fix similar problems with eager loading,
there was another edge case that got accidentally fixed as well.
The issue is this:
In JoinAssociation#aliased_table_name_for, the following code is run to
generate an aliased table name:
name = connection.table_alias_for
#{pluralize(reflection.name)}_#{parent_table_name}#{suffix}
table_index = aliases[name] + 1
name = name[0, connection.table_alias_length-3] + _#{table_index} if
table_index 1
After this, aliases[name] is incremented. But since the value of name is
now the new, aliased table name, the effect is that we end up with an aliases
hash that looks something like this (taken from a multiply self-referential
parent-child join:
{
people=1, children_people=1,
children_people_2=2, parents_people=1,
parents_people_2=2
}
As you can see, instead of counting aliases against children_people, we began
counting against the aliased table name itself. This leads the JoinDependency
to create invalid JoinAssociations (2 against children_people_2 and
parents_people_2 in this case, which means twice it incremented
children_people and landed on the same table name), and creates table name
collisions.
The patch at
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/6423
fixes the regression and adds a test to cover it in the future.
--
Ernie Miller
http://metautonomo.us
http://github.com/ernie
http://twitter.com/erniemiller
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: rails 3.0.4 broke yield :javascript ?
Great, ping me if I can help you. BTW did you tried 3-0-stable? On Thu, Feb 10, 2011 at 9:51 AM, Joaquin Rivera Padron joahk...@gmail.com wrote: for me are broken also versions 3.0.4, 3.0.4.rc1, 3.0.3 and 3.0.2 ok is 3.0.1, will keep digging then jk 2011/2/9 Brian Morearty bmorea...@gmail.com Yes, I saw something similar when I upgraded to 3.0.4 this morning. I didn't have a chance to debug it so for the moment I went back to 3.0.1. I wasn't sure if it was my doing so I didn't say anything on this list. I have a helper function that returns an HTML string. The function calls .html_safe before returning. That worked in 3.0.1 but in 3.0.4 it is being escaped in the output. I also tried adding .html_safe to the .html.erb file (double-safe it) but to no avail. I was not able to reproduce it in a simple case though, even in very same function. Brian On Feb 9, 1:06 pm, Joaquin Rivera Padron joahk...@gmail.com wrote: hello, I have today updated my rails app to 3.0.4 security release but now this yield :javascripts fails in the layout and I get my custom js escaped as text in the view. anybody seeing this also? tia, jk --www.least-significant-bit.com -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- www.least-significant-bit.com -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: rails 3.0.4 broke yield :javascript ?
This commit
https://github.com/rails/rails/commit/2c8bff3513b17a8ad55595a61601bfba14ad40bf
just changes from html_escape string to ERB::Util.html_escape(string)
so both are calling the same method.
You're talking about this one
https://github.com/rails/rails/commit/bb9c58eb4aa637fa75c69c705a9918d6322ff834
and this fix a security issue. I'd say that you're missing a html_safe
some where.
On Thu, Feb 10, 2011 at 10:54 AM, Joaquin Rivera Padron
joahk...@gmail.com wrote:
commit 2c8bff3513b17a8ad55595a61601bfba14ad40bf
Author: Santiago Pastorino santi...@wyeworks.com
Date: Tue Nov 2 20:18:22 2010 -0200
Call as ERB::Util.html_escape since is not the module is not included
here
2011/2/10 Joaquin Rivera Padron joahk...@gmail.com
hi,
I diff-ed 3.0.0 with 3.0.1 and I got this
diff --git a/actionpack/lib/action_dispatch/routing/polymorphic_routes.rb
b/actionpack/lib/action_dispatch/routing/polymorphic_routes.rb
index 142cd08..fb2118a 100644
--- a/actionpack/lib/action_dispatch/routing/polymorphic_routes.rb
+++ b/actionpack/lib/action_dispatch/routing/polymorphic_routes.rb
@@ -17,7 +17,7 @@ module ActionDispatch
#
...skipping...
buffer = with_output_buffer { value = yield(*args) }
if string = buffer.presence || value and string.is_a?(String)
- NonConcattingString.new(string)
+ NonConcattingString.new(ERB::Util.html_escape(string))
end
end
if I put bac k the NonConcattingString.new(string) it works (at least for
me)
don't know the implications though, wdyt?
jk
2011/2/10 Joaquin Rivera Padron joahk...@gmail.com
yes, if by 3-0-stable you mean 3.0.0, yes it works
thanks for the ping offer, I'll let you know if anything, but I won't
(can't) be full time chasing the bug :-(
jk
2011/2/10 Santiago Pastorino santi...@wyeworks.com
Great, ping me if I can help you.
BTW did you tried 3-0-stable?
On Thu, Feb 10, 2011 at 9:51 AM, Joaquin Rivera Padron
joahk...@gmail.com wrote:
for me are broken also versions 3.0.4, 3.0.4.rc1, 3.0.3 and 3.0.2
ok is 3.0.1, will keep digging then
jk
2011/2/9 Brian Morearty bmorea...@gmail.com
Yes, I saw something similar when I upgraded to 3.0.4 this morning. I
didn't have a chance to debug it so for the moment I went back to
3.0.1. I wasn't sure if it was my doing so I didn't say anything on
this list.
I have a helper function that returns an HTML string. The function
calls .html_safe before returning. That worked in 3.0.1 but in 3.0.4
it is being escaped in the output.
I also tried adding .html_safe to the .html.erb file (double-safe it)
but to no avail.
I was not able to reproduce it in a simple case though, even in very
same function.
Brian
On Feb 9, 1:06 pm, Joaquin Rivera Padron joahk...@gmail.com wrote:
hello,
I have today updated my rails app to 3.0.4 security release but now
this
yield :javascripts
fails in the layout and I get my custom js escaped as text in the
view.
anybody seeing this also?
tia,
jk
--www.least-significant-bit.com
--
You received this message because you are subscribed to the Google
Groups
Ruby on Rails: Core group.
To post to this group, send email to
rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
www.least-significant-bit.com
--
You received this message because you are subscribed to the Google
Groups
Ruby on Rails: Core group.
To post to this group, send email to
rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
You received this message because you are subscribed to the Google
Groups Ruby on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
www.least-significant-bit.com
--
www.least-significant-bit.com
--
www.least-significant-bit.com
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email
Re: [Rails-core] ActiveModel::AttributeMethods limiting
Hey Alex, if you want go ahead and try a fix ;). On Sat, Feb 5, 2011 at 4:37 AM, Alex alexander.uva...@gmail.com wrote: In my attempt to add AM:Dirty to my model I realized that AM#AttributeMethods is a bit imperfect. It's impossible to generate attribute methods step-by-step in DataMapper-like manner. class Model include ActiveModel::Dirty def self.property(name, klass = String) define_property_accessors(name, klass) # This method will be called once, because of https://github.com/rails/rails/blob/master/activemodel/lib/active_model/attribute_methods.rb#L263 define_attribute_methods([name]) end end class Article Model property :title property :body property :published_at, Time end In the above example, attribute methods will be defined just for :title. I don't see any nice workaround. So what is the purpose of AttributeMethods#attribute_methods_generated? I can't imagine any use case for this. What about removing it entirely and providing #define_attribute_method(s) with ability to call it multiple times? Am I missing something? -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
You're not late guys, I'm still compiling information. On Sat, Feb 5, 2011 at 1:16 PM, kdevdatta kane.devda...@gmail.com wrote: Hi, Seems that I am a bit late to the party. But I can contribute to the following ones - 1. exception_notification 2. auto_complete 3. in_place_edit 4. country_select 5. dynamic_form So if you guys need some help maintaining any one these, I would be very glad to help. I am also open for any other plug-in also. Regards, Devdatta -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
Hey Everton, Sorry I didn't mentioned in my mail but rails_upgrade was made by Jeremy McAnally, I'm not sure if he is maintaning it though. So it's outside of scope, anyways if you're interested perhaps you can ping him :). Cheers. On Thu, Feb 3, 2011 at 3:38 PM, EMoreth everton.mor...@gmail.com wrote: I would like to take rails_upgrade https://github.com/emoreth/rails_upgrade I believe that this one can be very usefull to make the whole community upgrade. And it can also be used to ease deprecation of old methods. Everton Moreth On Feb 3, 4:36 am, Anuj Dutta dutta.a...@googlemail.com wrote: Hello there, I am willing to take responsibility of any plugin really and have no particular preference. Please give a shout once you have made a decision. Thanks. Anuj On 2 February 2011 19:38, Steven Soroka ssorok...@gmail.com wrote: https://github.com/ssoroka/ssl_requirement https://github.com/ssoroka/ssl_requirementI'd take this plugin; the api for ssl is really clunky. I haven't pushed any changes to my fork yet, but I think this could be implemented with before_filters, giving us :only / :except, and :if / :unless support, and supporting skip_before_filter. On Feb 1, 2011, at 10:04 PM, Santiago Pastorino wrote: We are looking for maintainers for the rails plugins listed in http://github.com/railsexcept arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.comrubyonrails-core%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- Anuj DUTTA -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
Sorry I think I forget to answer this email, rails_xss is out of scope. Please pick another one :). On Wed, Feb 2, 2011 at 1:30 PM, ABK abhikumar...@gmail.com wrote: being interested in Application-Security and Rails... I'd love maintaining rails_xss On Feb 2, 9:04 am, Santiago Pastorino santi...@wyeworks.com wrote: We are looking for maintainers for the rails plugins listed inhttp://github.com/railsexcept arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
The list for now is ... (I'll be waiting for more to give the possibility for more but I think we are good to go) We need the repo info for the ones of Prem Sichanugrist, Lars Smit, BrianBommarito (TokenGenerator) As you can see there are some projects with more than one person willing to do it I propose to open one repo only and make you guys work together, what do you think?. For example we can give Chris Lerum country_select if Chris provides push access to Mark Turner. Prem Sichanugrist verification (waiting for you repo info) hide_action (waiting for you repo info) dynamic_form (waiting for you repo info) Trevor Bramble https://github.com/TrevorBramble/atom_feed_helper Darian Shimy https://github.com/dshimy/http_authentication Mark Turner https://github.com/amerine/country_select https://github.com/amerine/acts_as_list https://github.com/amerine/acts_as_tree https://github.com/amerine/in_place_editing Jason King https://github.com/JasonKing/exception_notification Lars Smit http_authentication (waiting for you repo info) ssl_requirement plugins (waiting for you repo info) Joel Moss http://codaset.com/joelmoss/dynamic-form BrianBommarito https://github.com/bbommarito/acts_as_nested_set https://github.com/bbommarito/account_location TokenGenerator (waiting for you repo info) Chris Lerum https://github.com/chrislerum/country_select John Dewey https://github.com/retr0h/ssl_requirement Steven Soroka https://github.com/ssoroka/ssl_requirement Anuj Dutta no particular preference I'd say if you don't mind check the list and choose the projects when you see you could be helpful ;). If more people want to help we can give them push access to the repos you guys have. Thanks! On Fri, Feb 4, 2011 at 11:20 AM, Santiago Pastorino santi...@wyeworks.com wrote: Sorry I think I forget to answer this email, rails_xss is out of scope. Please pick another one :). On Wed, Feb 2, 2011 at 1:30 PM, ABK abhikumar...@gmail.com wrote: being interested in Application-Security and Rails... I'd love maintaining rails_xss On Feb 2, 9:04 am, Santiago Pastorino santi...@wyeworks.com wrote: We are looking for maintainers for the rails plugins listed inhttp://github.com/railsexcept arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
You're not late I will be waiting more for people to join. So please comment which plugins you want to take care of. On Fri, Feb 4, 2011 at 3:57 PM, Rishav Rastogi rishav.rast...@gmail.com wrote: Oh, I guess I am late to the party. :) I am ready to help/share responsibility if anybody needs it. Cheers Rishav On Fri, Feb 4, 2011 at 11:14 PM, Mark Turner m...@amerine.net wrote: On Fri, Feb 4, 2011 at 5:27 AM, Santiago Pastorino santi...@wyeworks.com wrote: For example we can give Chris Lerum country_select if Chris provides push access to Mark Turner. Sounds great. -Mark -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- Rishav Rastogi http://twitter.com/rishavrastogi Cell : +91 9980616888 Gtalk : rishav.rastogi Skype : rishavrastogi -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Looking for maintainers of Rails plugins
I'm glad to see you guys proposing to take over the plugins. I will wait more time for more people to propose themselves and then publish a list of the projects and maintainers. On Wed, Feb 2, 2011 at 2:27 PM, John Dewey jdew...@gmail.com wrote: https://github.com/retr0h/ssl_requirement On Feb 1, 8:04 pm, Santiago Pastorino santi...@wyeworks.com wrote: We are looking for maintainers for the rails plugins listed inhttp://github.com/railsexcept arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] Looking for maintainers of Rails plugins
We are looking for maintainers for the rails plugins listed in http://github.com/rails except arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Looking for maintainers of Rails plugins
Prem, cool but the idea is to have it outside the scope of rails. So please everyone interested fork the project you're interested in and send the address to your fork. After the call I will compile a list with each repo and the maintainers. Cheers. 2011/2/2 Prem Sichanugrist sikand...@gmail.com: I'll take verification, hide_action and dynamic_form because I was the one who extracted it. I already have the commit access to those, so will make sure they're up-to-date then. Prem On 2 ก.พ. 2554, at 11:04, Santiago Pastorino wrote: We are looking for maintainers for the rails plugins listed in http://github.com/rails except arel, jquery-ujs, prototype-ujs, rails_xss and rails itself :). The idea is that use your fork as official and make the rails ones point to your repo. Please reply telling us which project are you interested in and send us the url of your fork. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Rails 3 no longer URI escaping [ and ]
Fixed here https://github.com/rails/rails/commit/52b71c01fd3c8a87152f55129a8cb3234190734a Thanks you Jeremy ;). On Tue, Nov 16, 2010 at 6:25 PM, Jeremy Evans jeremyeva...@gmail.com wrote: On Sun, Oct 10, 2010 at 8:36 PM, Michael Koziarski mich...@koziarski.com wrote: Is it breaking your app some how? It breaks some test code, that's all. Test code that works on 5 other web frameworks and previous versions of Rails. It's not a big deal either way, but I wanted to know rails-core opinion before I decide whether to update my test code. I'll see if I can get something a bit more definitive from josh as to why this was changed. Seems a toss up either way, but the current method is certainly a bit messy and at the very least we shouldn't be escaping / unescaping It's been a month since this was last discussed, and there doesn't appear to have been any related changes made. Should I add a issue to lighthouse so that it's easier to keep track of this? Jeremy -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
[Rails-core] Fwd: [railsbridge] Postponed: Bugmash December 3-5
-- Forwarded message -- From: Dan Pickett dan.pick...@gmail.com Date: Tue, Nov 16, 2010 at 3:23 PM Subject: [railsbridge] Postponed: Bugmash December 3-5 To: railsbri...@googlegroups.com This must have not of made it through moderation for some reason. Would anyone be willing to help out with a late January/early February bugmash? Thanks, Dan On Tue, Nov 9, 2010 at 11:06 AM, Dan Pickett dan.pick...@gmail.com wrote: Hi all, I've been speaking with core team, and Santiago has really been instrumental in facilitating a date for another Bugmash. I'd like to have it on the 3rd - 5th of December. For the uninitiated, a Bugmash is when we get a bunch of people together to help resolve issues in the Core issue tracker. All are welcome to participate, help out, and learn how to contribute to Rails. I'm looking for volunteers to help. I need help with: * Manning the IRC chat room during the event to field questions and issues * Seeking prizes * Distributing prizes * Working on the application * maintaining the application during the Bugmash This is a great way to get involved in the Rails community at large. Santiago, who is now a Core Team member, started his contributions during a Bugmash. I'd love for Railsbridge to have a strong showing during this event. Best, -- = Dan Pickett Principal Enlight Solutions, Inc http://EnlightSolutions.com http://www.twitter.com/dpickett -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] FormHelper and write-only fields
I'm about to push a change related with this but definitely is not
going to solve your problem. You need a database field or a field
reader. Also your code doesn't work even before my commit. You can
check it out ...
Let's review it ...
object.respond_to?(method_name + _before_type_cast) ?
object.send(method_name + _before_type_cast) :
object.send(method_name)
Your object doesn't respond_to password_before_type_cast so this code
ends trying to execute object.send('password') and you don't have a
reader neither.
Oliver, perhaps what you want to do is f.password_field :password, :value = ''
and instead of writing the password= method you can do attr_writer :password ;)
I hope my message can clarify the situation.
Cheers,
Santiago.
On Fri, Aug 27, 2010 at 7:16 AM, Ernie Miller er...@metautonomo.us wrote:
FormHelper needs a read method, too. You can return a blank string if
you like but you need to respond_to the field name in question.
You're most likely doing something that's not playing nicely with this
commit's change to value_before_type_cast:
http://github.com/rails/rails/commit/fb0bd8c1092db51888ec4bb72af6c595e13c31fa
On Aug 27, 2010, at 4:55 AM, Oliver Eilhard oliver.eilh...@gmail.com wrote:
Hi!
Until recently I used a User model with a write-only password field on
it. The idea is to pick that cleartext password up, perform some
salting and hashing on it and then write that to the database. So my
model used a method like this:
def password=(cleartext_password)
�...@password = cleartext_password
end
Worked fine in combination with form_for and
f.password_field :password. But RC2 changed that and now complains
about missing method password_before_type_cast. The only workaround
I've found is to implement that method. (See
https://rails.lighthouseapp.com/projects/8994/tickets/5471-formhelper-problem-with-write-only-fields
for a diff with a failing test in actionpack.)
Can anybody shed some light on this?
Thank you,
Oliver
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: Routing error/difference between RC and Beta4
Did you open an issue for this? if not would you mind to do it so it can be discussed there?. Thanks. On Wed, Aug 4, 2010 at 10:15 AM, Ned rails.n...@gmail.com wrote: Just tried my project from scratch and generated using rails RC, rather than just changing the version in the Gemfile. Didn't work, but was worth testing :) If anyone has an idea, or a thought of why this change was made, would be good to hear cheers :) On Aug 2, 6:56 pm, Ned rails.n...@gmail.com wrote: In beta4 I could do this: resources :sections do get :new, :on=:member end But not with RC If I change new to be something else, it will work So it seems that new is now treated like a reserved word of sorts? I really need to share the new method between sections/new and sections/1/new because my structure is a tree, so it makes sense to re-use Example /section/1/new/ is so much cleaner (and dry) compared to /section/new/?parent=1 or /section/1/new_child Anyone have an opinion or suggestion? cheers! -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] How to disable ORM in Rails 3
Rodrigo, you should run ruby bin/rails --help --dev or ruby -rubygems bin/rails --help But you're right the error message was not the best it was fixed here http://github.com/rails/rails/commit/514624e53c7b3008e3c492ef01f4d85188cdbbd7 Cheers, Santiago. On Sun, Jul 25, 2010 at 9:49 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Thank you, Santiago. gem install bundler --pre allowed me to bundle install. But 'bin/rails --help' still yields: Thor is not available. If you ran this command from a git checkout of Rails, please make sure thor is installed, and run this command as `ruby /path/to/rails new myapp --dev` After running bundler, Thor is installed, as shown by gem list: *** LOCAL GEMS *** abstract (1.0.0) builder (2.1.2) bundler (1.0.0.beta.10) columnize (0.3.1) erubis (2.6.6) horo (1.0.0) i18n (0.4.1) json (1.4.3) linecache (0.43) mail (2.2.5) memcache-client (1.8.5) mime-types (1.16) mocha (0.9.8) mysql (2.8.1) nokogiri (1.4.2) pg (0.9.0) polyglot (0.3.1) rack (1.2.1) rack-mount (0.6.9) rack-test (0.5.4) rake (0.8.7) rdoc (2.5.9, 2.5.8) ruby-debug (0.10.3) ruby-debug-base (0.10.3) sqlite3-ruby (1.3.1) system_timer (1.0) text-format (1.0.0) text-hyphen (1.0.0) thor (0.13.8) treetop (1.4.8) tzinfo (0.3.22) yajl-ruby (0.7.7) Em 25-07-2010 21:40, Santiago Pastorino escreveu: Rodrigo, platforms were added to bundler 1.0.0.beta.10. Try with this version of bundler or master. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] How to disable ORM in Rails 3
Yes, it would be nice if --dev works everywhere. On Mon, Jul 26, 2010 at 9:18 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Santiago, now I could run bin/rails. But there is still something odd: ruby ~/src/git/rails/bin/rails --dev --help Thor is not available. If you ran this command from a git checkout of Rails, please make sure thor is installed, and run this command as `ruby /home/rodrigo/src/git/rails/bin/rails --help --help --dev` First, Thor is not available is a wrong statement. Then, it is odd that the --dev should be the last option... In fact, bin/rails --help --dev works. But bin/rails new /tmp/test -O --dev yielded: ... create vendor/plugins/.gitkeep run bundle install from . /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:235:in `resolve': undefined method `name' for nil:NilClass (NoMethodError) from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:338:in `resolve_requirement' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:337:in `catch' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:337:in `resolve_requirement' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:289:in `resolve' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:288:in `reverse_each' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:288:in `resolve' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:162:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:131:in `resolve' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:130:in `catch' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/resolver.rb:130:in `resolve' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/definition.rb:135:in `resolve' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/definition.rb:88:in `specs' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/definition.rb:83:in `resolve_remotely!' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/installer.rb:31:in `run' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/installer.rb:8:in `install' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/cli.rb:115:in `install' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor/task.rb:22:in `send' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor/task.rb:22:in `run' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor/invocation.rb:109:in `invoke' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor/invocation.rb:116:in `call' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor/invocation.rb:116:in `invoke' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor.rb:161:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor/base.rb:379:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/lib/bundler/vendor/thor.rb:140:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-1.0.0.beta.10/bin/bundle:13 from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/bin/bundle:19:in `load' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/bin/bundle:19 Maybe bundler beta 10 isn't enough... Anyway, it is not clear to me what the -O option changed in the output application files. Thank you once more. Rodrigo. Em 26-07-2010 15:28, Santiago Pastorino escreveu: Rodrigo, you should run ruby bin/rails --help --dev or ruby -rubygems bin/rails --help But you're right the error message was not the best it was fixed here http://github.com/rails/rails/commit
Re: [Rails-core] How to disable ORM in Rails 3
Agree -O should comment sqlite3-ruby patch it or create an issue ;). Thanks. On Mon, Jul 26, 2010 at 9:45 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Em 26-07-2010 21:18, Rodrigo Rosenfeld Rosas escreveu: ... Anyway, it is not clear to me what the -O option changed in the output application files. Ok, I've found the changes in config/application.rb. But I think sqlite3-ruby gem should be commented in Gemfile when -O is passed... Does it make sense? And maybe --disable-active-record should be named --disable-orm... Rodrigo. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] How to disable ORM in Rails 3
Rodrigo, platforms were added to bundler 1.0.0.beta.10. Try with this version of bundler or master. On Sun, Jul 25, 2010 at 9:35 PM, Rodrigo Rosenfeld Rosas rr.ro...@gmail.com wrote: Em 25-07-2010 18:01, Xavier Noria escreveu: On Sat, Jul 24, 2010 at 10:37 PM, Xavier Noriaf...@hashref.com wrote: Should be --skip-active-record, I'll revise that before RC together with the output of --help. Done, --skip-testunit has also been renamed to --skip-test-unit: http://github.com/rails/rails/commit/92669b8320a45e3f0497bfb83c0c8e55d515be0c Great! Maybe there should be some explanations on how to disable ORM after the project is created or how to enable ActiveRecord after the project has been created with --skip-active-record. Sometimes, one may start developing the UI and later then start using an ORM. It used to be explained how to disable ActiveRecord in Rails 2 environment.rb. Or maybe it is already done. It has been a while from the last time I used Rails master... I've just tried to, but couldn't test it: $ rvm gemset use defa...@rails-master --create $ git pull $ bin/rails --help Thor is not available. If you ran this command from a git checkout of Rails, please make sure thor is installed, and run this command as `ruby /path/to/rails new myapp --dev` Installing Thor wasn't enough for changing this message. Then, I guessed I should try bundle install. But it didn't work too: $ gem install thor $ gem install bundler $ bundle install /home/rodrigo/src/git/rails/Gemfile:22:in `evaluate': undefined method `platforms' for #Bundler::Dsl:0x7f470583e4f8 (NoMethodError) from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/definition.rb:12:in `from_gemfile' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler.rb:114:in `definition' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/cli.rb:91:in `install' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor/task.rb:33:in `send' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor/task.rb:33:in `run' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor/invocation.rb:109:in `invoke' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor/invocation.rb:116:in `call' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor/invocation.rb:116:in `invoke' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor.rb:137:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor/base.rb:378:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/lib/bundler/vendor/thor.rb:124:in `start' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/gems/bundler-0.9.26/bin/bundle:13 from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/bin/bundle:19:in `load' from /home/rodrigo/.rvm/gems/ruby-1.8.7-p...@rails-master/bin/bundle:19 Maybe it would be useful to include a new file README_FOR_GIT_MASTER. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] How to disable ORM in Rails 3
It's -O or --skip-activerecord rails new --help Usage: rails new APP_PATH [options] Options: -d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db) # Default: sqlite3 -J, [--skip-prototype] # Skip Prototype files -T, [--skip-testunit] # Skip TestUnit files [--dev]# Setup the application with Gemfile pointing to your Rails checkout -G, [--skip-git] # Skip Git ignores and keeps -m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL). -b, [--builder=BUILDER]# Path to an application builder (can be a filesystem path or URL) [--edge] # Setup the application with Gemfile pointing to Rails repository -r, [--ruby=PATH] # Path to the Ruby binary of your choice # Default: /usr/bin/ruby [--skip-gemfile] # Don't create a Gemfile -O, [--skip-activerecord] # Skip ActiveRecord files Runtime options: -p, [--pretend] # Run but do not make any changes -s, [--skip] # Skip files that already exist -q, [--quiet]# Supress status output -f, [--force]# Overwrite files that already exist Rails options: -h, [--help] # Show this help message and quit -v, [--version] # Show Rails version number and quit Description: The 'rails new' command creates a new Rails application with a default directory structure and configuration at the path you specify. Example: rails new ~/Code/Ruby/weblog This generates a skeletal Rails installation in ~/Code/Ruby/weblog. See the README in the newly created application to get going. Rodrigo, try Rails master. Cheers, Santiago. On Sat, Jul 24, 2010 at 5:37 PM, Xavier Noria f...@hashref.com wrote: Should be --skip-active-record, I'll revise that before RC together with the output of --help. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group.It's To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] error running rake test in actionpack
bundle update should make the tests work again. On Sun, Jul 18, 2010 at 1:31 PM, cageface milese...@gmail.com wrote: I get this error when I try to rake test in actionpack: (in /home/miles/c/rails/actionpack) /home/miles/c/rails/activesupport/lib/active_support/dependencies.rb: 212:in `require': no such file to load -- rack/mount (LoadError) from /home/miles/c/rails/activesupport/lib/active_support/ dependencies.rb:212:in `require' from /home/miles/c/rails/activesupport/lib/active_support/ dependencies.rb:198:in `load_dependency' from /home/miles/c/rails/activesupport/lib/active_support/ dependencies.rb:563:in `new_constants_in' from /home/miles/c/rails/activesupport/lib/active_support/ dependencies.rb:198:in `load_dependency' from /home/miles/c/rails/activesupport/lib/active_support/ dependencies.rb:212:in `require' from /home/miles/c/rails/actionpack/lib/action_dispatch/routing/ route_set.rb:1 Adding a clause like this: group :test do gem rack-mount end To the Gemfile seems to fix it. Is that the right solution or am I missing something? -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: helping with rails 3 release
You can help fixing issues on LightHouse yeah, but now Yehuda, Carl and Adré are putting a great effort to solve some issues on Bundler. I think now what is blocking the release is that Rails and Bundler should be delivered both together as RC and Bundler need some more work. So perhaps you can help there. On Wed, Jul 14, 2010 at 11:17 PM, Jeff cohen.j...@gmail.com wrote: On Jul 10, 2:19 pm, cageface milese...@gmail.com wrote: I'd like to pitch in and help get the rails 3 release out the door. Where is help most needed? I can fix bugs, edit docs, write tutorials etc. I've been working through the open tickets on lighthouse but it seems like the high priority stuff is mostly fixed. +1 Me too. Maybe I've missed something obvious, but I'm not exactly sure (from looking at lighthouse tix) what others are already working on (don't want to duplicate effort) vs. what might be helpful to work on (especially any docs that need updating, etc?) Thanks Jeff -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] [PATCH] validates_uniqueness_of does not quote scoped column names and then barfs
Could you open an issue on LH and attach a patch following the guidelines?
So core team can make the patch yours.
Thank you ;).
On Sat, Jun 19, 2010 at 12:50 PM, ara.t.howard ara.t.how...@gmail.comwrote:
this is a silly bug that breaks any code where the column name of a
scope is a reserved word (like group):
cfp:/opt/local/lib/ruby/gems/1.8/gems/activerecord-2.3.8 diff -buB
lib/active_record/validations.rb.org lib/active_record/validations.rb
--- lib/active_record/validations.rb.org2010-06-19
09:38:42.0 -0600
+++ lib/active_record/validations.rb2010-06-19 09:39:01.0
-0600
@@ -825,7 +825,7 @@
if scope = configuration[:scope]
Array(scope).map do |scope_item|
scope_value = record.send(scope_item)
- condition_sql AND
attribute_condition(#{record.class.quoted_table_name}.#{scope_item},
scope_value)
+ condition_sql AND
attribute_condition(#{record.class.quoted_table_name}.#{connection.quote_column_name(scope_item)},
scope_value)
condition_params scope_value
end
end
--
You received this message because you are subscribed to the Google Groups
Ruby on Rails: Core group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.comrubyonrails-core%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: [PATCH] validates_uniqueness_of does not quote scoped column names and then barfs
I replied your ticket asking to follow https://rails.lighthouseapp.com/projects/8994/sending-patches and to do a test case for this issue. Thank you ara.t.howard. On Sat, Jun 19, 2010 at 9:34 PM, ara.t.howard ara.t.how...@gmail.comwrote: On Jun 19, 1:07 pm, Santiago Pastorino santi...@wyeworks.com wrote: Could you open an issue on LH and attach a patch following the guidelines? So core team can make the patch yours. Thank you ;). https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4909-validates_uniqueness_of-does-not-quote-scoped-column-names-and-then-barfs -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.comrubyonrails-core%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] [PATCH] ActiveSupport OrderedHash Doesn't Support Passing Block to merge
I've done a tiny improvement to this implementation. Please Xavier review it ;). http://github.com/spastorino/rails/commit/63b43575765c7d4042c23ac3ddb1213c1968b5a3 On Sun, Jun 13, 2010 at 1:42 AM, Xavier Noria f...@hashref.com wrote: On Sun, Jun 13, 2010 at 4:42 AM, Xavier Noria f...@hashref.com wrote: Just realized the patch is not compatible with 1.9, since in 1.9 only existing keys are merged (that's the key? key test in Rubinius). Will revise it myself. Rather, yield is called only for existing keys. This revisions seems to be correct: http://github.com/rails/rails/commit/36143d26cb841210b5f22aff4ed9c093a0554a1a -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Should an blank string be html_safe?
Remember you can use raw for output unsafe strings without being escaped On Mon, May 17, 2010 at 4:07 PM, RobL pgdst...@googlemail.com wrote: Just trying to implement a simple helper over the past few days had me really confused. messages = '' messages content_tag(:p, 'dave') #= lt;pgt;davelt;\p%;gt; Eventually I realised the original empty string was not html_safe message = ''.html_safe message content_tag(:p, 'dave') #= pdave/p Is this intentional behavour? -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Ruby Summer of Code Project
Hey Federico, I was talking with Jeremy Kemper regarding to benchmarks and he points me to try to benchmark an existing open source app. For example port redmine or gemcutter to rails 3 (Jeremy already port redmine http://github.com/jeremy/redmine/commits/rails3 but it's from november) and benchmark one of this (perhaps Gemcutter is simpler) with Rails 2.3 and Rails 3.0 and build a comparison. What do you think?. You can find me on IRC, i'm spastorino if you want we can exchange more ideas and thoghts about this. Best, Santiago. On Tue, Apr 20, 2010 at 9:35 PM, Federico Builes federico.bui...@gmail.com wrote: On Tue, Apr 20, 2010 at 7:21 PM, Chad Woolley thewoolley...@gmail.com wrote: On Tue, Apr 20, 2010 at 2:56 PM, Jeremy Kemper jer...@bitsweat.net wrote: Hi Jeremy, Yes, good points. I've already talked with Federico offline. I believe his original interest was in improving the rails test suite itself, and allowing collaboration and submission of results by users. I think it is mostly orthogonal to the problem I'm tackling - which is to have a performant, stable, easily reproducible production CI environment which runs the main build script (http://github.com/rails/rails/blob/master/ci/ci_build.rb) against the major interpreters. I don't want to make the production CI environment any more complicated than necessary - and adding the variable of user-submitted input from random environments would definitely complicate things. It's hard enough to get most people to care about the failing CI at all - we need to keep it simple, stable, and reproducible. That's why I'm taking the approach of a Rails CI AMI which anyone can run on EC2, and the generation of that AMI will also be completely automated. That hopefully eliminates any possibility of non-reproducible build failures, which are the bane of any CI system. I've said reproducible four times, so you get my point :) However, as long as any improvements/innovations in this area (rake tasks, additional/alternative test/benchmark scripts to ci_build.rb, etc) conform to basic conventions - stdout/stderr, generated csv/html flat file artifacts, and proper return codes - there's no reason we can't integrate it into the main CI environment (or any other CI environment) in the future. Even if it isn't integrated, the information gathered can drive improvements to the main test suite or build script. However, I'd prefer avoid calling this work CI or lumping it into the CI effort, for the reasons mentioned above, and also because it would be more user driven than continuous. In fact, I've already updated the wiki to say Crowdsourced Rails environment compatibility metrics instead of continuous integration. As Chad mentioned, we've been exchanging emails outside the list and it's been helpful to ground my proposal. Some of my ideas can fall outside the current scope of Chad's work on a CI platform to build a pristine copy of Rails everytime but I think we can definately collaborate on some of the stuff to make sure all this is usable for the rails-core guys and for the outsider who just wants to see what's wrong with X revision on his machine. My idea is a bit more biased to what Jeremy initially noted but I'll keep working on it today/tomorrow to send a copy to the ML looking for input once it's done. Thanks for comments guys. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Rails3 beta3 is not installing properly
Fresh installation 2 minutes ago debian:~# gem install rails --pre Successfully installed activesupport-3.0.0.beta3 Successfully installed activemodel-3.0.0.beta3 Successfully installed actionpack-3.0.0.beta3 Successfully installed arel-0.3.3 Successfully installed activerecord-3.0.0.beta3 Successfully installed activeresource-3.0.0.beta3 Successfully installed actionmailer-3.0.0.beta3 Successfully installed railties-3.0.0.beta3 Successfully installed rails-3.0.0.beta3 9 gems installed Installing ri documentation for activesupport-3.0.0.beta3... Installing ri documentation for activemodel-3.0.0.beta3... Installing ri documentation for actionpack-3.0.0.beta3... Installing ri documentation for arel-0.3.3... Installing ri documentation for activerecord-3.0.0.beta3... Installing ri documentation for activeresource-3.0.0.beta3... Installing ri documentation for actionmailer-3.0.0.beta3... Installing ri documentation for railties-3.0.0.beta3... Installing ri documentation for rails-3.0.0.beta3... Installing RDoc documentation for activesupport-3.0.0.beta3... Installing RDoc documentation for activemodel-3.0.0.beta3... Installing RDoc documentation for actionpack-3.0.0.beta3... Installing RDoc documentation for arel-0.3.3... Installing RDoc documentation for activerecord-3.0.0.beta3... Installing RDoc documentation for activeresource-3.0.0.beta3... Installing RDoc documentation for actionmailer-3.0.0.beta3... Installing RDoc documentation for railties-3.0.0.beta3... Installing RDoc documentation for rails-3.0.0.beta3... On Wed, Apr 14, 2010 at 4:49 PM, Jeremy Kemper jer...@bitsweat.net wrote: On Wed, Apr 14, 2010 at 11:03 AM, spaquet spaque...@gmail.com wrote: Looks like documentation is not installing properly for Rails3 beta3. Here is the error I'm facing : Successfully installed rails-3.0.0.beta3 1 gem installed Installing ri documentation for rails-3.0.0.beta3... ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - lib Could you try uninstalling the previous beta gems first, then reinstalling the latest? jeremy -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] How do I get the right version to contribute to rails 2.3.x
You have to work on a clean copy of 2-3-stable branch. I saw your 5MB patch and i think you mix 2-3-stable things with master things. from scratch git clone git://github.com/rails/rails.git git checkout 2-3-stable and now you are on a clean 2-3-stable, patch as you patch on master. but do git format-patch 2-3-stable --stdout file.path On Mon, Mar 8, 2010 at 11:31 AM, Stijnster s.mathy...@telenet.be wrote: Hi all, I just got my first fix into rails (https://rails.lighthouseapp.com/ projects/8994/tickets/4080). And it tastes like more :-) Creating the patch for 3.0 was easy because the current master branch points to the 3.0 branch. But adding the fix to 2.3 was a bit difficult. I switched to the 2.3-stable branch, but that provided a patch file of around 5 Mbyte. Probably containing all patches since the last 2.3 stable version. What is the correct procedure to checkout the latest and active master version of rails 2.3? Stijn -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] Re: How do I get the right version to contribute to rails 2.3.x
You're welcome Stijnster, the patch was yours. I'm not a patch stealer :). On Mon, Mar 8, 2010 at 12:50 PM, Stijnster s.mathy...@telenet.be wrote: More than that, you even rectified it. Thanks for that! I just ran the default command to format the patch; git format-patch master --stdout your-patch-file.diff Now I see where I went wrong. Thanks a million! On Mar 8, 3:40 pm, Santiago Pastorino spastor...@gmail.com wrote: You have to work on a clean copy of 2-3-stable branch. I saw your 5MB patch and i think you mix 2-3-stable things with master things. from scratch git clone git://github.com/rails/rails.git git checkout 2-3-stable and now you are on a clean 2-3-stable, patch as you patch on master. but do git format-patch 2-3-stable --stdout file.path On Mon, Mar 8, 2010 at 11:31 AM, Stijnster s.mathy...@telenet.be wrote: Hi all, I just got my first fix into rails (https://rails.lighthouseapp.com/ projects/8994/tickets/4080). And it tastes like more :-) Creating the patch for 3.0 was easy because the current master branch points to the 3.0 branch. But adding the fix to 2.3 was a bit difficult. I switched to the 2.3-stable branch, but that provided a patch file of around 5 Mbyte. Probably containing all patches since the last 2.3 stable version. What is the correct procedure to checkout the latest and active master version of rails 2.3? Stijn -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Re: [Rails-core] run only one ruby test
On railties/test directory do ruby application/console_test.rb On Sat, Feb 13, 2010 at 8:44 PM, siong1987 siong1...@gmail.com wrote: for example, i want to run only one single test for edge. what command should i use?. the test i want to run is at the path: /railties/test/ application/console_test.rb any idea? Thank you. And, I am actually trying to patch https://rails.lighthouseapp.com/projects/8994/tickets/3822-reload-doesnt-reload . Is the ticket valid? -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. -- You received this message because you are subscribed to the Google Groups Ruby on Rails: Core group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
