SVN-repository — with rapidSVN (GUI)

rapidSVN is a cross platform subversion client. It’s project page is http://rapidsvn.tigris.org/
On Ubuntu you can install it from the package manager.

checkout with rapidSVN

  • Open rapidSVN
  • rightclick on bookmarks and choose “add existing repository”
  • use “https://svn.typo3.org/Teams/DocTeam/” as location
  • you can now browse the online repository
  • to check out parts of the repository right click on the folder you want to check out and choose “checkout new working copy”
  • select a folder (destination directory) to store your local copy and press OK

You could also checkout without creating any bookmarks first:

  • Choose repository from the top menu
  • Click checkout
  • Enter relevant information and press OK

 

tag the new version

  • navigate in the left bookmarks-folder to the manual you want to tag. e.g. “typo3_tut”
  • click at folder “tags” – and it gets orange
  • click at top menu “modify” and menu-item “create new folder”
  • naming style “Version-1-0-0”
  • navigate to the folder “trunk” and select all inside
  • right click and choose “copy”
  • type in YOUR LOCAL location: /path/to/your/local/copy/DocTeam/manual/tags/Version-1-0-0 (NO trailing slash!)
  • check with the browser: http://forge.typo3.org/repositories/show/team-docteam

 

Commit/upload the changes

  • if you made changes to your local files they are displayed orange in the rapidSVN browser
  • to commit your changes just right click on the file name and choose “commit”

 

remember: our server is

https://svn.typo3.org/Teams/DocTeam/

Advertisements

Best Practice 4 – Code should be written to be reviewed

While writing your software code, keep in mind that someone is going to review your code and you will have to face criticism about one or more of the following points but not limited to:

  • Bad coding
  • Not the following standard
  • Not keeping performance in mind
  • History, Indentation, Comments are not appropriate.
  • Readability is poor
  • Open files are not closed
  • Allocated memory has not been released
  • Too many global variables.
  • Too much hard coding.
  • Poor error handling.
  • No modularity.
  • Repeated code.

Keep all the above-mentioned points in your mind while coding and stop them before they jump in your source code. Once you are done with your coding, go for a self-review atleast once. I’m sure, a self-review would help you in removing 90% problems yourself.

Once you are completely done with your coding and self review, request your peer for a code review. I would strongly recommend to accept review comments happily and should be thankful to your code reviewers about the comments. Same time, it is never good to criticize any source code written by someone else. If you never did it, try it once and check the coder’s expression.