Design Rules

From Konversation

Jump to: navigation, search

konversationrc

  • When changing something that needs an UPD-script, write the code and the script at the same time and check-in in a single svn command; running UPD-scripts after the related keys have already been used by konvi can break a test environment and might have unpredictable results.
  • When changing syntax of a key, rename the key; otherwise running old versions of konvi can mess up the rc-file.

Check-in

  • Only check-in code that builds and runs nicely; the SVN trunk should always build and run.
  • When testing new code that might be incompatible with other stuff or instable or is not finally discussed or is otherwise in discussion, use branches; use branches as a shared sandbox if more than one coder is writing on a new idea.
Retrieved from "http://konversation.kde.org/wiki/Design_Rules"
Personal tools