Commits on May 2, 2011

1. I suggest that the link to the ChangeLog be a link to the appropriate… …

   … branch. The docs link already requires this step. What has been happening is the master branch ChangeLog has not been kept up to date as promptly, and during those times (now and the time mentioned here http://stackoverflow.com/questions/5522877/node-js-wheres-the-changelog-the-describes-v0-4-4-and-0-4-5). Also, a note should be made on whatever new-release-todo-list you have so when 0.5 comes along, this is updated. If this change is rejected, the home page of nodejs.org will likely continue to at times show an out of date ChangeLog. When this happened to me, I never found the new change log after serious looking around because I did not know about the other branches. Eventually the StackOverflow question found somebody who knew.

   

   GeorgeBailey committed May 2, 2011
   Configuration menu

   • View commit details
   • Copy full SHA for 5211507
   • Browse repository at this point

   Copy the full SHA

   5211507 View commit details

   Browse the repository at this point in the history