HOWTO: Test your commits and other guidelines




  • it says svn not sun

    Things to do before a commit:

    • Make sure everything works and that you haven’t added any exploits. The logic behind that is up to you.

    • Don’t commit if it doesn’t compile. If for some reason you need to save bad code to the server, make a branch and merge it once you’ve fixed it.

    • Update the changelog.html file in the html folder.

    Things to do after a commit:

    • Try compiling from a freshly exported* version of the codebase. You can do that with the SVN Tortoise repo browser or with the “svn export” command.

    • Fix or revert your commit if you fucked up. Don’t leave broken code on the HEAD version.

    • If you want the server’s binaries to be updated, post here: http://www.noxiousnet.com/forums/index.php?topic=16837.0

    *not a checkout! an export to a new folder




  • it says svn not sun

    Things to do before a commit:

    • Make sure everything works and that you haven’t added any exploits. The logic behind that is up to you.

    • Don’t commit if it doesn’t compile. If for some reason you need to save bad code to the server, make a branch and merge it once you’ve fixed it.

    • Update the changelog.html file in the html folder.

    Things to do after a commit:

    • Try compiling from a freshly exported* version of the codebase. You can do that with the SVN Tortoise repo browser or with the “svn export” command.

    • Fix or revert your commit if you fucked up. Don’t leave broken code on the HEAD version.

    • If you want the server’s binaries to be updated, post here: http://www.noxiousnet.com/forums/index.php?topic=16837.0

    *not a checkout! an export to a new folder



  • I’d like to reiterate that when you test your code you test it with a fresh export.



  • Updated.


Log in to reply
 

8
Online

11020
Users

15276
Topics

297661
Posts

Looks like your connection to NoXiousNet was lost, please wait while we try to reconnect.