cs2340:Team Development and Source Control

1
cs2340Team Development and Source Control

• Spring 2007

2
Configuration Management

• Planning
• Identification
• Control
• Status Accounting
• Evaluation
• Release Management and Delivery

3
Configuration Control

• Problem How to allow many developers to work on
  your code at the same time.
• Solution
• One Person One File
• Email notification
• Token Based (Coke Can)
• Source Control System (CVS, Subversion)

4
Configuration Decisions

• What do we control?
• When do we start to control it?
• How do we stay in sync?
• Tools only help with the last item.

5
Visualworks Solution

• Store
• See SourceCodeManagementControl.pdf
• Uses conventional database backend to maintain
  code organized in packages or parcels
• You may run your own database or register for the
  Cincom public Store

6
Registration Information

• Follow instructions in 4911 on-line manual
• http//www.cincomsmalltalk.com8008/launch/PostGre
  sRequest

7
Store

• Store keeps the Parent version of the code
• Developers Load a working version
• Changes are seen only on Developers local image.
• Put your changes to the Server with Publish
• Resolve conflicts with Merge

8
Versions

• Store assigns a new version with each publish
• Foo (1.1) ? Foo(1.2)? Foo(1.3)
• Sometimes two developers work at the same time
• Foo(1.1) Foo(1.2)
• Foo(1.2.1)

Foo(1.3)
9
Dividing the Work

• Dependency Management separate work for minimum
  dependencies
• Do not Divide work to organization
• Try to minimize Merges, they are a pain

10
Steps

• Register for your Store password
• Set up your login by making a login profile by
  selecting Store-gtRepository and entering your
  information
• Login to Store using your new profile
• One person on the team makes a configuration of
  bundle packages and any preliminary code that
  has been produced

11
Steps

• Right click on the bundle and select Publish
• Write out any comments you wish and then select
  Publish
• To start clean, right click your bundle and
  select Remove
• Then go to Store and select the version you want
  to work on. Right click and select Load.

12
Steps

• To look for changes/conflicts, select your method
  in the browser and right click to bring up menu.
  Select Store-gtCompareWith
• When both people have changes, we have to Merge.
• Load version on Store that will be the mainstream
  version

13
Steps

• Be sure blessing level is integration-ready
• Select Merge option with version to be used as
  base selected
• Resolve conflicts as needed and Publish