1 / 16

ITEC 370

ITEC 370. Lecture 16 Implementation. Review. Questions? Design document on F, feedback tomorrow Midterm on F Implementation Management (MMM) Team roles Code reviews / Pair programming. Objectives. Look at version control. Scenario. You spend 4 hours working on a feature

malik-hardin
Download Presentation

ITEC 370

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITEC 370 Lecture 16 Implementation

  2. Review • Questions? • Design document on F, feedback tomorrow • Midterm on F • Implementation • Management (MMM) • Team roles • Code reviews / Pair programming

  3. Objectives • Look at version control

  4. Scenario • You spend 4 hours working on a feature • Another teammate also spends 4 hours working on a feature • Both work • Both include changes to the same system • Which code should be accepted?

  5. Issues • What files are part of the repository • Who can modify each file • How are conflicts (merges) handled • Who can add files to the repository • Who can remove files from the repository • Are all changes logged so reversion is possible

  6. Updating • When you change the repository you can leave a message • Extremely useful in maintenance • Also useful for keeping track of developers

  7. Bad version control • Fruit can / USB key • Issues • Backup? • Source hog

  8. Types • Simple • Only one person can write at a time • Centralized • One server to rule them all • Distributed • Spread out all over the place

  9. Access • GUI • Integrated into IDE • Non-GUI • Command line app • Type in commands to handle it (preferred method)

  10. Git • Free for open source, low cost for private repositories • Distributed system • Local / remote repository • Supports branching and merging • Good for experiments • Takes extra effort

  11. Visually Alpha 1 Initial Prototype 1 Prototype 2

  12. Starting a repository in Git • First off create content • Second, store content in a directory • Commands • gitinit • git add . • git commit –m “Initial commit”

  13. Updating • Use git diff to see what is different between working copy and repository • Use git commit –a to add local changes to repository • Warning: Have to add new files manually • git –A . • Fun • git blame filename

  14. Remote repository • Want to get code from someone? • gitremote add origin git@github.com:vogella/gitbook.git • Switch to a different directory • gitclone --bare . path/gitbook.git • Want to send code to someone? • git push –u name master

  15. Guide • Excellent tutorial • Branching / merging • Specifics / examples http://www.vogella.com/articles/Git/article.html

  16. Review • Version control • Why • What is typically used • Example of Git

More Related