Meeting 3

Meeting 3: 01/08/19

• Coding Conventions

  • Comment while we code
  • NO UNDERSCORES
  • USE JAVADOC COMMENTS
  • CamelCase
  • No coding past the INTELLIJ line :))
  • Proper indentation

• Branch convention is feature/task based, we need to rename this.

• Good commit messages

• Test cases

  • Use JUnit
  • Good test names
  • Test code regularly, and before committing/merging
  • Integration Tests
  • Unit Tests

• Build tools

  • Maven

• Source Control

  • Pre-master branch(developer branch)
  • Always pull from pre-master branch everyday.
  • Pre master should be 100% working, but doesn’t matter if its not.
  • RELEASES ON THE MASTER ONLY - 100% always working
  • If two people pull from premaster at the same time, the 2nd person who commits to the pre master branch will have to pull from the premaster branch first and make the changes in their own code(branch) test in your own branch, and then merge back into pre-master.
  • Need everyone’s approval when we move from pre-master to master.
  • Commit for every update.
  • Don’t push every commit, push when the feature is completed.

• Algorithm Discussion

  • Inputs/Outputs
  • TilesFX for visualisation
    • https://github.com/HanSolo/tilesfx
  • A*, Branch And Bound
  • Possible Greedy algorithm for first implementation