Implement a versioning/change-log system so we know what changes have been published in pre and prod

[JuanMenendezBuitrago]

We should find a way to make it easy for everyone to know what changes they can expect (and test in pre). Some sort of change-log document maybe? When someone sets something as "ready to test" he/she could write on it what issue has been fixed and then when the code is deployed, someone responsible would edit the document so it reflects the date of the deployment and thus the last change that has been published.

This is more like a hand-made solution but I can't come up with anything else.

[marcosmenendez]

Why don't we use this tool together with our releases? https://github.com/posabsolute/releasenotes

I would imply that we need to review the issues included in a release before deploying it and move them forward if they haven't been deployed. What do you thing @atrandafir ?

[atrandafir]

I think this is not really a "changelog", at least not alone, this should be related to deployments.

I'm thinking of the following:

1. I go to a deployment tool, select environment, pre or prod, and click deploy
2. Now this tool looks at the repository/branch and makes a list of all the new commits since last deployment to that environment and another list of the issues mentioned in those commits
3. Somewhere this historical data is saved and we can later check it at any time

I think that should be what would provide us enough information so we know what happend and on what environment.

Right now for the deployments we use Capistrano. I'm not sure what extra tool we should add or how to deal with this but I've found some interesting links:
http://beanstalkapp.com/
https://developer.github.com/guides/delivering-deployments/
https://github.com/atmos/heaven

And a funny robot to who you can ask to run deployments and automated tasks:
https://hubot.github.com/

So looks like there are APIs and tools that could improve this process but further investigation would be required.