# Keeping track of changes to Rails **URL:** \ **Category:** Rails\ **Created:** [October 19, 2007, 7:29pm UTC](https://www.ruby-forum.com/t/keeping-track-of-changes-to-rails/117731 "2007-10-19T19:29:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bruz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5f8ce5/32.png) [@bruz](https://www.ruby-forum.com/u/bruz)\ **Post date:** [October 19, 2007, 7:29pm UTC](https://www.ruby-forum.com/t/keeping-track-of-changes-to-rails/117731/1 "2007-10-19T19:29:58Z")
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](http://edgenic.com/2007/10/19/tracking-edge-rails-changes)), but is there a better way? ---
**Author:** ![bruz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5f8ce5/32.png) [@bruz](https://www.ruby-forum.com/u/bruz)\ **Post date:** [October 19, 2007, 7:44pm UTC](https://www.ruby-forum.com/t/keeping-track-of-changes-to-rails/117731/2 "2007-10-19T19:44:01Z")
> 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](http://edgenic.com/2007/10/19/tracking-edge-rails-changes)), > but is there a better way? [http://ryandaigle.com/tags/Edge%20Rails](http://ryandaigle.com/tags/Edge%20Rails) Seems to be the link most people reference when this comes up… ---
**Author:** ![bruz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5f8ce5/32.png) [@bruz](https://www.ruby-forum.com/u/bruz)\ **Post date:** [October 19, 2007, 7:55pm UTC](https://www.ruby-forum.com/t/keeping-track-of-changes-to-rails/117731/3 "2007-10-19T19:55:44Z")
On 10/19/07, Bruz [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 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/](http://ryandaigle.com/) – Rick O. [http://lighthouseapp.com](http://lighthouseapp.com) [http://weblog.techno-weenie.net](http://weblog.techno-weenie.net) [http://mephistoblog.com](http://mephistoblog.com) ---
**Author:** ![bruz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5f8ce5/32.png) [@bruz](https://www.ruby-forum.com/u/bruz)\ **Post date:** [October 19, 2007, 7:56pm UTC](https://www.ruby-forum.com/t/keeping-track-of-changes-to-rails/117731/4 "2007-10-19T19:56:19Z")
On Oct 19, 2007, at 10:00 PM, Philip H. wrote: > > but is there a better way? > > [http://ryandaigle.com/tags/Edge%20Rails](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](http://peepcode.com/products/rails2-pdf) – fxn ---
**Author:** ![bruz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/5f8ce5/32.png) [@bruz](https://www.ruby-forum.com/u/bruz)\ **Post date:** [October 23, 2007, 12:17am UTC](https://www.ruby-forum.com/t/keeping-track-of-changes-to-rails/117731/5 "2007-10-23T00:17:18Z")
Thanks. I agree that Ryan does a stellar job of distilling out the most important changes in rails, and presents them quite well.