We do this - we run two week iterations, and group fixes and features under a
version number that tracks the iteration. Every commit is linked to an issue,
and every issue is linked to a release version. The last thing we do in an
iteration is a commit to bump the version number to match the ite
Indeed I don't think there's need to track "versions" on a web application,
since it's way more common for people to use tags or similar with git or
some other scm, when they do.
In any case, it's fairly easy to add that to your application if you want
or need it:
*module Todo*
* class Applicati
Hi Rain,
I don’t think that web applications are like software libraries in this
respect. Engineering teams that are pushing software out the door are already
tracking their versions with commits to their source control. SemVer is great
because it helps convey things like breaking changes, bu
every lib/gem will have a version, but seems everyone forgot the project
itself.
I preferred a config.version option in the applicaiton.rb after running rails
new
module Todo
class Application < Rails::Application
...
config.version = '1.0.0'
endend
then in rails console, we can
