Subversion Do and Don’ts

April 25, 2008 · Filed Under Dev Hours 

When developing on a project with subversion (or any other centralized revision control system) do not:

  • commit without useful log, unless you are not a human (eg: scripty)
  • pass 1 commit/minute commit rate

When developing on a project with subversion (or any other centralized revision control system) do:

  • Test your changes locally
  • Use a staging (devel) server

Tags:

Comments

7 Responses to “Subversion Do and Don’ts”

  1. herman saksono on April 25th, 2008 2:38 pm

    Ada apa e Ten? Kejadian di workplace? :D

    [Reply]

  2. Akhmad Fathonih on April 25th, 2008 2:41 pm

    hehehe, begitulah .. sh*ts happen :p

    [Reply]

  3. andaluzzia on April 28th, 2008 8:52 pm

    met ultah om ton :d
    all the best..
    *telat*

    [Reply]

  4. Kramero on April 30th, 2008 11:57 am

    subversion sucks… :P

    [Reply]

  5. Nico on May 6th, 2008 12:38 pm

    Hi Tony,
    Any idea how to apply those “suggestions” for facebook application development? I don’t think I could test locally while developing a facebook application :(

    [Reply]

    Akhmad Fathonih reply on 5/7/2008 3:07 pm:

    Hi Nico,
    Long time no see :). Of course my suggestion won’t work for Facebook App. That’s something you can blame to Facebook for not releasing a decent SDK. They should follow Google App Engine approach :)

    [Reply]

  6. adit on May 8th, 2008 6:03 pm

    numpang nambahin :D

    jangan commit kalau perubahan filenya gara2 spasi aja….. walaupun ndak ngaruh ke system,,, tapi its anoyying

    [Reply]

Leave a Reply