Pages tagged versioning:

django-reversion - Google Code
http://code.google.com/p/django-reversion/

"Version control for Django models"
Reversion is an extension to the Django web framework that provides comprehensive version control facilities.
Revision control for Django models. Might be useful for those times when I forget/neglect to add to SVN.
Ultimate Round-Up For Version Control with Subversion | Developer's Toolbox | Smashing Magazine
http://www.smashingmagazine.com/2009/03/10/ultimate-round-up-for-version-control-with-subversion/
by Glen Stansberry Subversion is a version control system that many Web developers and designers use to back up their work. Subversion was started in 2000 and is quite popular in the open-source community; major
AirBlog — A Paper Trail For Your Models
http://blog.airbladesoftware.com/2009/6/23/a-paper-trail-for-your-models
PaperTrail lets you track changes to your Rails app’s models’ data. It’s good for auditing or versioning. You can see how a model looked at any stage in its lifecycle and even undelete it after it’s been destroyed.
acts_as_versioned simply_audited
rvm: Ruby Version Manager - rvm Home
http://rvm.beginrescueend.com/
different interpreter versions easily
You want to try out all of the different ruby interpreters and versions including different patchlevels, but you don't want to break what's working for you now. No time to waste?
managing versions of ruby
pimping out git log - Bart's Blog
http://www.jukie.net/~bart/blog/pimping-out-git-log
Très joli git log --graph à consommer sans modération
You can run the following to add it to your ~/.gitconfig: git config --global alias.lg "log --graph --pretty=format:'%Cred%h%Creset
I love this custom log view for git
You Don't Know Jack About Software Maintenance | November 2009 | Communications of the ACM
http://cacm.acm.org/magazines/2009/11/48444-you-dont-know-jack-about-software-maintenance/fulltext
Article which seems nice. I should read.
No direct references are allowed to anything if they can be avoided. Every data structure is designed for expansion and self-identifying as to version. Every code segment is made self-identifying by the compiler or other construction procedure. Code and data are changeable on a per-command/process/system basis, and as few as possible copies of anything are kept, so single copies could be dynamically updated as necessary.
Semantic Versioning
http://semver.org/
GitHub
How to version your API correctly so other developers don't get into dependency hell.
"Under this scheme, version numbers and the way they change convey meaning about the underlying code and what has been modified from one version to the next."
Ce document spécifie une manière de numéroter les versions qui je trouve intelligente.
Database Versioning
http://adam.blog.heroku.com/past/2009/3/2/database_versioning/
Migrations bother me. On one hand, migrations are the best solution we have for the problem of versioning databases. The scope of that problem includes merging schema changes from different developers, applying schema changes to production data, and creating a DRY representation of the schema. But even though migrations is the best solution we have, it still isn’t a very good one.
Check the brainstorming at the end. I love where he's going. Short version: a schema.yml file identified by its SHA1 hash. Migrations are for translating data between versions. Great comments at the end by the smart people in the community.
On one hand, migrations are the best solution we have for the problem of versioning databases. The scope of that problem includes merging schema changes from different developers, applying schema changes to production data, and creating a DRY representation of the schema.