# \[ANN\] Rails 3.0 Beta ALL PLEASE READ

**URL:** <https://www.ruby-forum.com/t/ann-rails-3-0-beta-all-please-read/183070>\
**Category:** Rails\
**Created:** [February 7, 2010, 3:01pm UTC](https://www.ruby-forum.com/t/ann-rails-3-0-beta-all-please-read/183070 "2010-02-07T15:01:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![conz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/a5b964/32.png) [@conz](https://www.ruby-forum.com/u/conz)\
**Post date:** [February 7, 2010, 3:01pm UTC](https://www.ruby-forum.com/t/ann-rails-3-0-beta-all-please-read/183070/1 "2010-02-07T15:01:12Z")

</div>

Hi ALL, for all the early adopters of Rails 3.0 Beta, I’m sure that  
means  
most if not all of you. Anyway, I would highly recommend reading and  
following the below steps:

1. Release Notes

2. Online Community Support

3. Filing Tickets Issues/Tickets Against Rails 3.0 Beta

/overview

```
 b) if (a) exists, then add your comments to that ticket. 

```

Otherwise,  
please create a new ticket providing the following:

```
      - create a proper title that briefly describes the issue
      - ruby version (i.e. ruby -v)
      - OS version
      - the exact steps to recreate the issue in a understandable

```

stepwise format  
- properly tag the ticket  
- For example, if it’s an issue with Rails 3.0  
ActiveRecord,  
then, at a minimum, I should see the following tags for the ticket:

```
           rails3 activerecord

  Note: This is very important so that the Rails core team are made

```

aware of the potential issue(s) as soon as possible. The  
more issue(s) that are detected and resolved before the  
official release make for a much more stable release. Again,  
you should have read (1).

Lastly, I would recommend the above steps for all people interested  
using  
Rails 3.0 Beta. Also, please reference (1) because it will change as we  
come to the official release of Rails 3.0.

-Conrad