Hi all, I know that it''s supposed to be good practice as a Rails developer to keep track of changes in Edge Rails in case there are bug fixes or new pieces functionality that can help you out. I''m wondering how folks generally do this. Various blogs do a good job of posting on key changes and how nifty they are, but this only captures bits and pieces. For the moment I''m just watching Subversion commits (as described in my post http://edgenic.com/2007/10/19/tracking-edge-rails-changes), but is there a better way? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On Oct 19, 2007, at 10:00 PM, Philip Hallstrom wrote:> >> I know that it''s supposed to be good practice as a Rails developer to >> keep track of changes in Edge Rails in case there are bug fixes or >> new >> pieces functionality that can help you out. I''m wondering how folks >> generally do this. Various blogs do a good job of posting on key >> changes and how nifty they are, but this only captures bits and >> pieces. For the moment I''m just watching Subversion commits (as >> described in my post http://edgenic.com/2007/10/19/tracking-edge- >> rails-changes), >> but is there a better way? > > http://ryandaigle.com/tags/Edge%20Rails > > Seems to be the link most people reference when this comes up...There''s a booklet recently published as well: http://peepcode.com/products/rails2-pdf -- fxn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 10/19/07, Bruz <bruz.marzolf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Hi all, > > I know that it''s supposed to be good practice as a Rails developer to > keep track of changes in Edge Rails in case there are bug fixes or new > pieces functionality that can help you out. I''m wondering how folks > generally do this. Various blogs do a good job of posting on key > changes and how nifty they are, but this only captures bits and > pieces. For the moment I''m just watching Subversion commits (as > described in my post http://edgenic.com/2007/10/19/tracking-edge-rails-changes), > but is there a better way? >You can get changesets as an rss feed from trac. Or, you could sit back and let Ryan gather the info for you: http://ryandaigle.com/ -- Rick Olson http://lighthouseapp.com http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
> I know that it''s supposed to be good practice as a Rails developer to > keep track of changes in Edge Rails in case there are bug fixes or new > pieces functionality that can help you out. I''m wondering how folks > generally do this. Various blogs do a good job of posting on key > changes and how nifty they are, but this only captures bits and > pieces. For the moment I''m just watching Subversion commits (as > described in my post http://edgenic.com/2007/10/19/tracking-edge-rails-changes), > but is there a better way?http://ryandaigle.com/tags/Edge%20Rails Seems to be the link most people reference when this comes up... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks. I agree that Ryan does a stellar job of distilling out the most important changes in rails, and presents them quite well. On Oct 19, 10:50 am, Xavier Noria <f...-xlncskNFVEJBDgjK7y7TUQ@public.gmane.org> wrote:> On Oct 19, 2007, at 10:00 PM, Philip Hallstrom wrote: > > > > >> I know that it''s supposed to be good practice as a Rails developer to > >> keep track of changes in Edge Rails in case there are bug fixes or > >> new > >> pieces functionality that can help you out. I''m wondering how folks > >> generally do this. Various blogs do a good job of posting on key > >> changes and how nifty they are, but this only captures bits and > >> pieces. For the moment I''m just watching Subversion commits (as > >> described in my posthttp://edgenic.com/2007/10/19/tracking-edge- > >> rails-changes), > >> but is there a better way? > > >http://ryandaigle.com/tags/Edge%20Rails > > > Seems to be the link most people reference when this comes up... > > There''s a booklet recently published as well: > > http://peepcode.com/products/rails2-pdf > > -- fxn--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---