[Rails-core] Approximate release timeline for Rails 4?
Is there any targeted date for release of Rails 4? Best I could find Googling was "in 2012", but that could mean anything from days to months. Asking because I've been running across some obscure bugs (https://github.com/rails/rails/issues/7809 for instance) in the course of a larger patch, and am curious if it would be better to split the bugs out as individual issues (happens sooner) or fix them in a bigger patch (takes longer). Thanks, --Matt Jones -- 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] Approximate release timeline for Rails 4?
Soonish. There are some things that are blocking the release, but they're being worked on. There's no set date. All the major pieces are in place. > am curious if it would be better to split the bugs out as individual issues > (happens sooner) or fix them in a bigger patch (takes longer). Always split them up into the smallest possible things. Makes them easier to review, makes them easier to write, makes it easy to pick and choose between portions. -- 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] Approximate release timeline for Rails 4?
On 1 October 2012 00:43, Steve Klabnik wrote: > Soonish. There are some things that are blocking the release, but > they're being worked on. There's no set date. All the major pieces are > in place. > > > am curious if it would be better to split the bugs out as individual > issues (happens sooner) or fix them in a bigger patch (takes longer). > > Always split them up into the smallest possible things. Makes them > easier to review, makes them easier to write, makes it easy to pick > and choose between portions. > Talking of patches, is there any chance that someone could look at PR #6450 please. It's to do with routing. It's over 4 months old but I rebased it yesterday. If anyone has a couple of free minutes, could they pull it or let me know what needs changing please? https://github.com/rails/rails/pull/6450/ Thanks, 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-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] Approximate release timeline for Rails 4?
Any Rails release timeline announcements are generally wrong, anyway. On Monday, 1 October 2012 at 9:49 AM, Jeremy Walker wrote: > > > On 1 October 2012 00:43, Steve Klabnik (mailto:st...@steveklabnik.com)> wrote: > > Soonish. There are some things that are blocking the release, but > > they're being worked on. There's no set date. All the major pieces are > > in place. > > > > > am curious if it would be better to split the bugs out as individual > > > issues (happens sooner) or fix them in a bigger patch (takes longer). > > > > Always split them up into the smallest possible things. Makes them > > easier to review, makes them easier to write, makes it easy to pick > > and choose between portions. > > Talking of patches, is there any chance that someone could look at PR #6450 > please. It's to do with routing. It's over 4 months old but I rebased it > yesterday. If anyone has a couple of free minutes, could they pull it or let > me know what needs changing please? > > https://github.com/rails/rails/pull/6450/ > > Thanks, 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-core@googlegroups.com > > (mailto:rubyonrails-core@googlegroups.com). > > To unsubscribe from this group, send email to > > rubyonrails-core+unsubscr...@googlegroups.com > > (mailto:rubyonrails-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-core@googlegroups.com > (mailto:rubyonrails-core@googlegroups.com). > To unsubscribe from this group, send email to > rubyonrails-core+unsubscr...@googlegroups.com > (mailto: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.
