Documentation related TODO when publishing a new version

Versions.md

@@ -10,10 +10,15 @@
   * Check if no unclassed bug should belong to current milestone.
 2. Update documentation (or make sure it is up to date)
 3. Update changelog
-4. Look for every instance of old version number in the repository, and update the relevant ones.
+4. Look for every instance the following items in the repository, and update the relevant ones:
+  * previous version number;
+  * year of previous version (to update stuff like `Copyright 2012 The Patacrep team`);
+  * the word `TODO`.
 5. Build and publish packages (tar.gz, Debian/Ubuntu, Windows, etc.)
 6. Update README
   * Installation
   * Look for other outdated information
 7. Apply git tag
-8. Advertise the new version
+8. Look for `TODO` in the documentation, and update links to installation packages if necessary.
+9. Apply git tag to the documentation.
+10. Advertise the new version