On Tue, Nov 15, 2011 at 6:36 AM, Mislav <[email protected]> wrote:
> Rails 3.1.2.rc2 just got released. Around the time of the 3.1.1 release, > there was also a relatively evolved release process including announcements > and release candidates. > > Why? > Standardizing the process makes it easier to manage frequent releases. Pushing a candidate is part of making that process robust and repeatable. In other words, bugfix releases are cheap. Why waste time with release > candidates when we can just get 3.1.2 right away? Then, every fix that > would otherwise be made between 3.1.2.rc2-3.1.2 can just be released as > 3.1.3. > The candidates are to avoid release screwups, not to capture every last possible bug. (3.1.2.rc1, for example.) I love the spirit behind doing point releases like crazy and recovering quickly from issues with new point releases. But our experience shows that actually leads to *less frequent* releases. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
