So do Rails, ActiveRecord, Rack, NokoGiri, Cucumber, among others.
<http://stackoverflow.com/questions/7532285/which-format-should-the-version-constant-of-my-project-have>

Steve Klabnick recommends the same.  He also recommends putting that
library's VERSION constant into a version.rb.
<http://timelessrepo.com/making-ruby-gems>

Which likewise is the approach Rails uses.

<http://guides.rubyonrails.org/initialization.html#railties-lib-rails-version-rb>


On Sat, Nov 12, 2011 at 12:25 AM, Ryan Davis <ryand-ruby / zenspider.com> wrote:
>
> On Nov 11, 2011, at 20:20 , Chad Perrin wrote:
>
>> Using a constant could prove problematic.  ¨Âóáéä éî áî åáòìéå>> response:
>>
>>  ¨Â§í õóéîôèÇåíººÖåòóéïî ôèéîæïîïéî ðáòô âåãáõóɧöå óååî
>>  ¨Âáóåó ÷èåòæïóïíå òåáóïî ÖÅÒÓÉÏãïîóôáîô ãïîæìéãô÷éôè
>>  ¨Âïíåôèéîç åìóå éî ôèÒõâù åîöéòïîíåîô®  ¨Â èáöåî§óååî éô éî ñõéô>>  ¨Âèéìåâõäïî§÷áîô ôï èáöå ôï äåáì ÷éôè ôèáô ëéîä ïæ éóóõå®
>
> According to my stats, I've got 526 releases that all use this pattern and I've never once had a problem with using the VERSION constant. "could prove problematic" sounds like urban legend to me more than a real issue.
>
>
>



-- 
Carina