Rails - Mar 2005 - Getting started with contributing to Rails

Hi,

If I wanted to help contribute to the development on Rails (with
software, not money :-), what would be a good starting point?  More
unit tests?  Documentation?

Thanks,
Joe

Joe Van Dyk wrote:
> If I wanted to help contribute to the development on Rails (with
> software, not money :-), what would be a good starting point?  More
> unit tests?  Documentation?
Comprehensive unit tests and documentation are at least as (if not more)
valuable than new features.  Here are some bugs which need fixes and tests:
  http://dev.rubyonrails.com/report/1

Thanks for pitching in!
jeremy

wow, theres alot of bugs to be fixed there, I''ll have to keep this 
report handy if I''m going to use rails

Jeremy Kemper wrote:
>Joe Van Dyk wrote:
>  
>
>>If I wanted to help contribute to the development on Rails (with
>>software, not money :-), what would be a good starting point?  More
>>unit tests?  Documentation?
>>    
>>
>
>Comprehensive unit tests and documentation are at least as (if not more)
>valuable than new features.  Here are some bugs which need fixes and tests:
>  http://dev.rubyonrails.com/report/1
>
>Thanks for pitching in!
>jeremy
>_______________________________________________
>Rails mailing list
>Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>http://lists.rubyonrails.org/mailman/listinfo/rails
>  
>

On Wed, 09 Mar 2005 14:52:34 -0800, Francisco Hernandez
<lagcisco-b7MHZcQsHeJWk0Htik3J/w@public.gmane.org>
wrote:
> wow, theres alot of bugs to be fixed there, I''ll have to keep this
> report handy if I''m going to use rails
> 
> Jeremy Kemper wrote:
> 
> >Joe Van Dyk wrote:
> >
> >
> >>If I wanted to help contribute to the development on Rails (with
> >>software, not money :-), what would be a good starting point?  More
> >>unit tests?  Documentation?
> >>
> >>
> >
> >Comprehensive unit tests and documentation are at least as (if not
more)
> >valuable than new features.  Here are some bugs which need fixes and
tests:
> >  http://dev.rubyonrails.com/report/1
> >
> >Thanks for pitching in!
> >jeremy
> >_______________________________________________
Yeah.  Although, you probably won''t ever run into most of those bugs
on a typical application.

Thats like 1 defect in 500 lines of code. Thats nothing :)
> wow, theres alot of bugs to be fixed there, I''ll have to keep this
> report handy if I''m going to use rails

1 : 5 isn''t uncommon. 

-- 
Tobi
http://www.snowdevil.ca - Snowboards that don''t suck
http://www.hieraki.org   - Open source book authoring
http://blog.leetsoft.com - Technical weblog

> wow, theres alot of bugs to be fixed there, I''ll have to keep this
> report handy if I''m going to use rails
This list has bugs of higher priorities:
http://dev.rubyonrails.com/report/9

Michael Koziarski has been working hard weeding out tickets and 
promoting the most important ones to this list. So any work done on the 
tickets here will directly take us closer to a 1.0 release.
--
David Heinemeier Hansson,
http://www.basecamphq.com/   -- Web-based Project Management
http://www.rubyonrails.org/  -- Web-application framework for Ruby
http://www.loudthinking.com/ -- Broadcasting Brain

Whats the difference between severity and priority?

David Heinemeier Hansson wrote:
>> wow, theres alot of bugs to be fixed there, I''ll have to keep
this
>> report handy if I''m going to use rails
>
>
> This list has bugs of higher priorities:
> http://dev.rubyonrails.com/report/9
>
> Michael Koziarski has been working hard weeding out tickets and 
> promoting the most important ones to this list. So any work done on 
> the tickets here will directly take us closer to a 1.0 release.
> -- 
> David Heinemeier Hansson,
> http://www.basecamphq.com/   -- Web-based Project Management
> http://www.rubyonrails.org/  -- Web-application framework for Ruby
> http://www.loudthinking.com/ -- Broadcasting Brain
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

Francisco Hernandez wrote:
> Whats the difference between severity and priority?
Severity tells you how nasty the bug is (crash, wrong behavior, 
cosmetic, etc)

Priority tells you how important it''s to get it fixed quickly.

example: if you have a windows application that crashes the OS, but 
strictly on a specific unpatched build of a danish localization of 
windows 98, than that''s a bug of high severity but low priority.