tag:help.rubygems.org,2010-01-19:/discussions/suggestions/2-display-of-changelog-file-per-versionRubyGems.org: Discussion 2011-04-07T20:59:24Ztag:help.rubygems.org,2010-01-19:Comment/9006062010-01-23T21:03:54Z2010-01-23T21:03:54ZDisplay of CHANGELOG file per version<div><p>My experience with YAML in ruby and RubyGems has shown me that
it is worst possible format you can use to store data. Furthermore,
having a YAML file for this data causes it to be entered twice,
once for human consumption and once for machine consumption.</p>
<p>Hoe's History.txt file is superior to YAML, IMO</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/9006062010-01-23T23:17:14Z2010-01-23T23:17:14ZDisplay of CHANGELOG file per version<div><p>Right. Like I said, the implementation can change, but the idea
is to have a format that Gemcutter can easily parse, which gem
authors stick to in order to get this information displayed. It
would be a really nice addition to the gem version pages.</p></div>Kieran Ptag:help.rubygems.org,2010-01-19:Comment/9006062010-01-23T23:20:52Z2010-01-23T23:20:52ZDisplay of CHANGELOG file per version<div><p>It would be nice to piggyback off an accepted standard, such
as:</p>
<p><a href=
"http://www.gnu.org/software/emacs/manual/html_node/emacs/Format-of-ChangeLog.html">
http://www.gnu.org/software/emacs/manual/html_node/emacs/Format-of-...</a></p>
<p>In any case, we don't extract any information from the built
gems as is right now. Both this and readmes would be the first, and
should be approached similarly. It would be nice to have full text
search on each. All of this has been in the pipeline for a while,
just no one's picked up lead on it. I'd be willing to help in any
way, but stability of the service has been my <a href=
"/discussions/suggestions/1" title="Discussion #1">#1</a> priority
as of late.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/9006062010-01-23T23:28:50Z2010-01-23T23:28:52ZDisplay of CHANGELOG file per version<div><p>You are welcome to grab the changelog patterns from Echoe:
<a href=
"http://github.com/fauna/echoe/blob/master/lib/echoe.rb#L171">http://github.com/fauna/echoe/blob/master/lib/echoe.rb#L171</a>
. Hoe/Jeweler probably have a similar facility.</p>
<p>It doesn't have to be a machine format; gem authors can choose
to conform if they want.</p></div>Evan