From: Intransition <transfire@...>
Date: 2011-11-13T12:01:26+09:00
Subject: Re: referring to version numbers in a gem

------=_Part_2356_8361947.1321153283493
Content-Type: multipart/alternative; 
	boundary="----=_Part_2357_22897051.1321153283494"

------=_Part_2357_22897051.1321153283494
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

@yossef 

As a developer/project-manager it's more desirable to keep all the 
project's metadata in a single source, and up at the toplevel of the 
project.

The constant is added only b/c that's become the expected norm, and Ruby 
lacks any standard protocol for accessing library metadata.

What I do more specifically is more advanced. All my projects has a 
standard metadata file that I interface to the code.


------=_Part_2357_22897051.1321153283494
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

@yossef&nbsp;<div><br></div><div>As a developer/project-manager it's more desirable to keep all the project's metadata in a single source, and up at the toplevel of the project.<div><br></div><div>The constant is added only b/c that's become the expected norm, and Ruby lacks any standard protocol for accessing library metadata.</div><div><br></div></div><div>What I do more specifically is more advanced. All my projects has a standard metadata file that I interface to the code.</div><div><br></div>
------=_Part_2357_22897051.1321153283494--

------=_Part_2356_8361947.1321153283493--