Corning Community College
Data Structures
Commits 1-2: Orientation in the class Backgammon Project
Objective
To ensure familiarity induce potential questions related to participating in, and developing the class Backgammon project.
Background
We've been spending time lately exploring the concepts and applications of version control, especially in relation to our class Backgammon project.
In order for this project to effectively kick off, everyone in the class needs to be familiar with how the system works, and that experience best comes with real, actual development on the project.
Procedure
By the start of class Tuesday, October 26th, 2010 (prior to 10:12AM on that day), I would like everyone to have completed the following:
- Perform 1 commit to the repository of a unique piece of class code.
- Commit as a separate file, to avoid conflicts.
- Perform 1 additional commit to the repository, for a total of at least 2 commits.
- Can also be a contribution of class code, or some typo fixing, or a test application, etc. Some relevant repository code update.
- Contribute relevant documentation to the Project wiki page.
- Wiki Edit MUST be in main wiki document, not in discussion board to count.
- any questions related to this assignment must be asked in a sanctioned forum of communication (class mailing list, class irc) sufficiently prior to our class on Tuesday.
Remember: A commit should be based on a relatively small change in the code (1 function being created, a couple of typos, etc.) Do NOT make massive changes and push them to the repository in 1 commit. That makes it considerably more difficult to track changes. You also don't have to be concerned with perfection.. your code does not need to compile this point… focus on content first, then we'll hammer out details later.
Submission
To complete this assignment, all you have to do is perform the above actions.