Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  Roland Moriz April 11th, 2010 @ 03:14 AM

  somone missed to upload the 2.3.5 gem to rubyforge I guess

  I think today it's even better to link to http://rubygems.org/gems/rails instead of rubyforge.

• 

  Ryan Bigg April 11th, 2010 @ 03:26 AM

  • Assigned user set to “Pratik”

  I agree here. Assigning to lifo. iirc, he's got the power to change the site.

• 

  Ryan Bigg April 11th, 2010 @ 02:14 PM

  • Assigned user changed from “Pratik” to “José Valim”

  Jose, Pratik said to "talk to Jose". Just following his advice.

• 

  José Valim April 11th, 2010 @ 02:18 PM

  I think it should point to Github downloads instead:

  http://github.com/rails/rails/downloads

• 

  José Valim April 11th, 2010 @ 02:20 PM

  • Assigned user changed from “José Valim” to “Pratik”

  Ryan, I don't have access to the website, so you can assign all tickets related to ror.org to DHH. All the others, I will be glad to help if I can.

• 

  José Valim April 11th, 2010 @ 02:22 PM

  • Assigned user changed from “Pratik” to “DHH”

  Assigning to DHH.

• 

  Mike Riley July 29th, 2010 @ 07:48 PM

  • Importance changed from “” to “Low”

  Hello,

  I have to agree that the downloads page (http://rubyonrails.org/download) should point to this rubygems.org page:

  http://rubygems.org/gems/rails/versions

  The link for "stand-alone packages" shows this page: http://rubyforge.org/frs/?group_id=307 which doesn't have anything after 2.3.4.

  Mike Riley

• 

  Ryan Bigg October 11th, 2010 @ 04:53 AM

  DHH (or anybody): please update download page to point to http://rubygems.org/gems/rails/versions rather than Rubyforge.

• 

  Ryan Bigg October 19th, 2010 @ 08:25 AM

  Automatic cleanup of spam.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:48 PM

  • State changed from “new” to “open”

  This issue has been automatically marked as stale because it has not been commented on for at least three months.

  The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

  Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:48 PM

  • State changed from “open” to “stale”