Introduction
The minimal amount of guidelines and structure to keep the project organized.
Details
- If doing a code reformat, make that change a single atomic checkin in SVN - don't reformat the code and make functional changes at the same time. (this makes it hard to separate out the real changes when viewing a diff later.)
- When doing an SVN checkin (or WIKI entry) please note the issue number it's related to (if there is an issue tracker number for the change) google code can automatically create links if you do this! for example, a Subversion comment for a checkin might be: *"Issue 5; make the xyz widget use the abc algorithm"*
- and vice versa, note the SVN revision number in the Issue comments when closing/changing an Issue.
(from http://code.google.com/p/support/wiki/WhatsNew : "Autolinking of issues Software development is all about putting ideas into working software. It turns out that the software created has a lot of interconnections, and the process of creating that software requires even more connections, dependencies, and references between all the information produced as part of the project. Google code hosting has always offered the developers the ability to link web pages in subversion, and wiki pages. We also encourage the use of Google groups or other mailing list archives that make past messages accessible via a link. And, every issue has had a clear URL that can be linked to, but only by specifying the full link. Now, you can easily and automatically link to any issue from another issue comment or from a wiki page. Just write "issue N" or "issue #N" and it will be linked to the corresponding issue in your project. If that issue is closed, the link text will be crossed out. oving your mouse over the link shows the summary of the issue. ")