<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dne 15.6.2011 19:28, Mo Morsi napsal(a):
<blockquote cite="mid:4DF8EBC8.2070908@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 06/14/2011 02:06 AM, Vít Ondruch wrote:
<blockquote cite="mid:4DF6FA5F.1030400@redhat.com" type="cite">
<pre wrap="">We should probably submit Rails 3.1 as a feature for F16. Any volunteer?
I am volunteering to do the packaging as soon as the stable version gets
released.
</pre>
</blockquote>
<br>
Hrm the stable rails 3.1 version is expected to be released in a
little over a week unless there are any setbacks [1]<br>
<br>
Here's the thing, I feel that most upstream communities are slowly
pushing towards migrating from Rails 2.3.x to 3.0.x. I have heard
almost nothing about Rails 3.1.x in production as of now (as is
expected since it hasn't been released).<br>
</blockquote>
<br>
From my POV, if they did not migrated to Rails 3 yet, then holding
back with upgrade to Rails 3.1 doesn't have sense. Also, I believe
that you should be able to install the F15 Rails on F16 if you like
the older version. If updating, why not the bleeding edge? Updating
to 3.0.x version doesn't bring anything new.<br>
<br>
Vit<br>
<br>
<br>
<br>
<blockquote cite="mid:4DF8EBC8.2070908@redhat.com" type="cite"> So
it might make sense to hold off on the update to 3.1 until we see
more upstream projects starting to adopt it and give feedback. Of
course we can always go the 'bleeding edge' route to be able to
say we are one of the first platforms to perform that update, but
we already can say that with our current Rails 3.0.x stack, and it
might make sense to stabilize around that a bit before updating
further.<br>
<br>
Of course if there are no incompatibilities, this probably won't
be a big deal, but I'm not sure if this is the case (the Rails
community does seem to be getting better at this). Again things
also may only be discovered as more upstream users start using
Rails 3.1 in their own projects. Looking at the changelogs
[2][3][4][5][6], there are things that at first glance could lead
to issues:<br>
<br>
* ActiveSupport::Dependencies now raises NameError if it finds an
existing constant in load_missing_constant.<br>
<div style="background-color: transparent;" class="line" id="LC15"><br>
* PostgreSQL adapter only supports PostgreSQL version 8.2 and
higher.<br>
<br>
* It is prohibited to perform a in-place SafeBuffer mutation
(actionpack)<br>
<br>
* Rely on Rack::Session stores API for more compatibility across
the Ruby world. This is backwards incompatible since
Rack::Session expects #get_session to accept 4 arguments and
requires #destroy_session instead of simply #destroy.
(actionpack)<br>
<br>
* The default format has been changed to JSON for all requests.
If you want to continue to use XML you will need to set
`self.format = :xml` in the class (activeresource)<br>
<br>
* jQuery is no longer vendored, it is provided from now on by
the jquery-rails gem. (railties)<br>
<br>
<br>
Some of these may not be an issue, but others warrant looking
into before we update.<br>
</div>
<br>
-Mo<br>
<br>
<br>
<br>
[1]
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://weblog.rubyonrails.org/2011/6/9/ann-rails-3-1-0-rc4-has-been-released">http://weblog.rubyonrails.org/2011/6/9/ann-rails-3-1-0-rc4-has-been-released</a><br>
[2] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/rails/rails/blob/master/activesupport/CHANGELOG">https://github.com/rails/rails/blob/master/activesupport/CHANGELOG</a><br>
[3] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/rails/rails/blob/master/activerecord/CHANGELOG">https://github.com/rails/rails/blob/master/activerecord/CHANGELOG</a><br>
[4] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/rails/rails/blob/master/actionpack/CHANGELOG">https://github.com/rails/rails/blob/master/actionpack/CHANGELOG</a><br>
[5] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/rails/rails/blob/master/activeresource/CHANGELOG">https://github.com/rails/rails/blob/master/activeresource/CHANGELOG</a><br>
[6] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/rails/rails/blob/master/railties/CHANGELOG">https://github.com/rails/rails/blob/master/railties/CHANGELOG</a><br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
ruby-sig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ruby-sig@lists.fedoraproject.org">ruby-sig@lists.fedoraproject.org</a>
<a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/mailman/listinfo/ruby-sig">https://admin.fedoraproject.org/mailman/listinfo/ruby-sig</a></pre>
</blockquote>
<br>
</body>
</html>