Hey Guys, We''ve had a rough few point releases in the 2.3 series. As a result I know there are people who are sitting on earlier releases rather than running 2.3.10. This is obviously not ideal. Especially for a release series that''s in long-term maintenance mode. So to fix all that I''d like to put a bunch of effort into tidying up the 2-3-stable branch to remove most / all of the upgrade blockers that people have hit. This will let people upgrade to 2.3.11 and pick up the bugfixes and security fixes which have been applied to that release. It''ll also set us up nicely for any future bugs that get fixed. So, if you have a 2.3.x application which can''t be upgraded to 2.3.10 ( or 2-3-stable as of today ) please reply to this thread and include a link to a lighthouse ticket so we can take a look. -- Cheers Koz -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Thank you, this is excellent news. You already applied the patch that fixes the issue we had with 2.3.10, but we''ll check out the latest 2.3-stable. On Mon, Nov 8, 2010 at 12:03 AM, Michael Koziarski <michael@koziarski.com> wrote:> Hey Guys, > > We''ve had a rough few point releases in the 2.3 series. As a result I > know there are people who are sitting on earlier releases rather than > running 2.3.10. This is obviously not ideal. Especially for a > release series that''s in long-term maintenance mode. > > So to fix all that I''d like to put a bunch of effort into tidying up > the 2-3-stable branch to remove most / all of the upgrade blockers > that people have hit. This will let people upgrade to 2.3.11 and pick > up the bugfixes and security fixes which have been applied to that > release. It''ll also set us up nicely for any future bugs that get > fixed. > > So, if you have a 2.3.x application which can''t be upgraded to 2.3.10 > ( or 2-3-stable as of today ) please reply to this thread and include > a link to a lighthouse ticket so we can take a look. > > > > -- > Cheers > > Koz > > -- > 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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Mon, Nov 8, 2010 at 11:03 AM, Michael Koziarski <michael@koziarski.com> wrote:> So, if you have a 2.3.x application which can''t be upgraded to 2.3.10 > ( or 2-3-stable as of today ) please reply to this thread and include > a link to a lighthouse ticket so we can take a look.https://rails.lighthouseapp.com/projects/8994/tickets/5568-239-destroy_all-destroys-loaded-records-that-do-not-match-the-scope-on-associations 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
This is on my TODO list for the next few days, will report back shortly. - Ken On Nov 7, 2010, at 5:03 PM, Michael Koziarski wrote:> Hey Guys, > > We''ve had a rough few point releases in the 2.3 series. As a result I > know there are people who are sitting on earlier releases rather than > running 2.3.10. This is obviously not ideal. Especially for a > release series that''s in long-term maintenance mode. > > So to fix all that I''d like to put a bunch of effort into tidying up > the 2-3-stable branch to remove most / all of the upgrade blockers > that people have hit. This will let people upgrade to 2.3.11 and pick > up the bugfixes and security fixes which have been applied to that > release. It''ll also set us up nicely for any future bugs that get > fixed. > > So, if you have a 2.3.x application which can''t be upgraded to 2.3.10 > ( or 2-3-stable as of today ) please reply to this thread and include > a link to a lighthouse ticket so we can take a look. > > > > -- > Cheers > > Koz > > -- > 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+unsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
This one is broken between 2.3.6 and 2.3.10.... https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5873-fix-broken-rack-params-parser-in-rails-236#ticket-5873-5 On Tue, Nov 9, 2010 at 9:36 AM, Ken Collins <ken@metaskills.net> wrote:> > This is on my TODO list for the next few days, will report back shortly. > > - Ken > > On Nov 7, 2010, at 5:03 PM, Michael Koziarski wrote: > > > Hey Guys, > > > > We''ve had a rough few point releases in the 2.3 series. As a result I > > know there are people who are sitting on earlier releases rather than > > running 2.3.10. This is obviously not ideal. Especially for a > > release series that''s in long-term maintenance mode. > > > > So to fix all that I''d like to put a bunch of effort into tidying up > > the 2-3-stable branch to remove most / all of the upgrade blockers > > that people have hit. This will let people upgrade to 2.3.11 and pick > > up the bugfixes and security fixes which have been applied to that > > release. It''ll also set us up nicely for any future bugs that get > > fixed. > > > > So, if you have a 2.3.x application which can''t be upgraded to 2.3.10 > > ( or 2-3-stable as of today ) please reply to this thread and include > > a link to a lighthouse ticket so we can take a look. > > > > > > > > -- > > Cheers > > > > Koz > > > > -- > > 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+unsubscribe@googlegroups.com<rubyonrails-core%2Bunsubscribe@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+unsubscribe@googlegroups.com<rubyonrails-core%2Bunsubscribe@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.