I''d like to pitch in and help get the rails 3 release out the door. Where is help most needed? I can fix bugs, edit docs, write tutorials etc. I''ve been working through the open tickets on lighthouse but it seems like the high priority stuff is mostly fixed. -- 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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Jul 10, 2:19 pm, cageface <milese...@gmail.com> wrote:> I''d like to pitch in and help get the rails 3 release out the door. > Where is help most needed? I can fix bugs, edit docs, write tutorials > etc. > > I''ve been working through the open tickets on lighthouse but it seems > like the high priority stuff is mostly fixed.+1 Me too. Maybe I''ve missed something obvious, but I''m not exactly sure (from looking at lighthouse tix) what others are already working on (don''t want to duplicate effort) vs. what might be helpful to work on (especially any docs that need updating, etc?) Thanks Jeff -- 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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
You can help fixing issues on LightHouse yeah, but now Yehuda, Carl and Adré are putting a great effort to solve some issues on Bundler. I think now what is blocking the release is that Rails and Bundler should be delivered both together as RC and Bundler need some more work. So perhaps you can help there. On Wed, Jul 14, 2010 at 11:17 PM, Jeff <cohen.jeff@gmail.com> wrote:> On Jul 10, 2:19 pm, cageface <milese...@gmail.com> wrote: >> I''d like to pitch in and help get the rails 3 release out the door. >> Where is help most needed? I can fix bugs, edit docs, write tutorials >> etc. >> >> I''ve been working through the open tickets on lighthouse but it seems >> like the high priority stuff is mostly fixed. > > +1 Me too. Maybe I''ve missed something obvious, but I''m not exactly > sure (from looking at lighthouse tix) what others are already working > on (don''t want to duplicate effort) vs. what might be helpful to work > on (especially any docs that need updating, etc?) > > Thanks > Jeff > > -- > 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 rubyonrails-core@googlegroups.com. > To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > >-- 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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
On Sat, Jul 10, 2010 at 3:19 PM, cageface <milesegan@gmail.com> wrote:> I''d like to pitch in and help get the rails 3 release out the door. > Where is help most needed? I can fix bugs, edit docs, write tutorials > etc. > > I''ve been working through the open tickets on lighthouse but it seems > like the high priority stuff is mostly fixed.Since nobody else has brought it up, one way you can help is to verify that plugins work on 3.0, fix any issues that arise, and (most importantly) report any pain points or bugs that you find in 3.0 itself. --Matt Jones -- 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 rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
One particular bit of functionality that has little API docs is
calling #render in the short way, like
render "new"
It''s a concrete task that is needed in the docs front if you''d
like to
help here.
The documentation from docrails/master is periodically generated here
http://edgeapi.rubyonrails.org/
In fact, if I am not mistaken (just did some browsing and ack''ing) the
docs of #render have been eaten by some refactoring vortex.
--
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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.