public write access for docrails is back

rubyonrails-docs
1

Subject says it all. Enjoy!

2

Thanks Xavier! That’s awesome.

This morning I began to add a link to the Guides home page to the release notes for Rails 3.1, but after a “git pull” I found someone else had already done that.

Do you think you can do a quick merge to master and push an updated version? I think a lot of folks will be looking for the release notes today.

(I also thought about putting the release notes in a more prominent place near the top section, but wasn’t sure if that would be acceptable. I can do that today if desired.)

Thanks,

Jeff

3

Cool! Great job bringing it back!

4

Nice to hear :slight_smile:

5

Thanks Xavier! That's awesome. This morning I began to add a link to the Guides home page to the release notes for Rails 3.1, but after a "git pull" I found someone else had already done that. Do you think you can do a quick merge to master and push an updated version? I think a lot of folks will be looking for the release notes today.

Yeah, I pushed them this morning, together with some very last minute changes to the asset pipeline guide. Docs are per release and this is really exceptional, but seemed worthwhile in this particular case.

Thanks for keeping an eye into this anyway :).

(I also thought about putting the release notes in a more prominent place near the top section, but wasn't sure if that would be acceptable. I can do that today if desired.)

Hmmm, there's a section for release notes, and they have been tweeted a lot.

I think we can keep the current structure. When a user comes to the guides home page I want them to see content, top-down explanations of how things work, right there. Release notes are published as guides for coherence, once you have the guides is a natural tool to use for that, but since they are announced with releases, and they are secondary to the website itself, I think it is better to have a discrete section for them for people that know where to look for them.

6

Yeah, I pushed them this morning, together with some very last minute

changes to the asset pipeline guide. Docs are per release and this is

really exceptional, but seemed worthwhile in this particular case.

Excellent.

Hmmm, there’s a section for release notes, and they have been tweeted a lot.

I think we can keep the current structure. When a user comes to the

guides home page I want them to see content, top-down explanations of

how things work, right there. Release notes are published as guides

for coherence, once you have the guides is a natural tool to use for

that, but since they are announced with releases, and they are

secondary to the website itself, I think it is better to have a

discrete section for them for people that know where to look for them.

Makes total sense. I figured you had already thought about this, which I think is why I hesitated to change it. Good thing I did. :slight_smile:

Jeff