Documenting update pushes, revisions, etc.

[choksi81]

I find it confusing that there seems to be little documentation available on when and why updates are pushed onto which part of the system. Similarly, it is difficult to reconstruct which revision of a file one currently has installed on a system. I do run into this issue quite often as I amend / instrument / modify my installation regularly for debugging purposes. Revision marking would also help to remote-debug installations.

My suggestion is to look at existing Trac tools (milestones maybe, or simple Wiki pages) that lets us structure the update process, including of course all of the thoughts, tickets, patches that lead up to it.

For marking revisions automatically, SVN provides a technique called ''keyword substitution''. This enables special keywords like $Id$ and $Revision$ to be substituted for their current values at checkout.