Integration neuer Versionsverwaltungssysteme
Outline
Saros weiss momentan nichts über das Vorhandensein von Versionsverwaltungswerkzeugen. Dabei wäre eine Nutzung der Team Synchronization Views in Saros zu Reviewzwecken wünschenswert. Ausserdem könnte das Versionsarchiv für die Synchronisierung von Projekten herangezogen werden. Perforce, SVN und Mercurial (hg) sind die am häufigsten nachgefragten SCMs.
Schedule
| Past |
 |
CW |
Goals  |
accomplished  |
 |
1 |
CWXX |
Goals |
accomplished |
…
Weekly Reports
Week ? (CW 20)
Activities
Results
- Checkout (rev. X) to Project programmatically.
- Create Patch for Project programmatically.
Problems
- The only API for "Apply Patch to Project" uses a Wizard.
- Create Patch only works on files under version control.
Week ? (CW 21)
Activities
- Release week
- Test manager
Results
Week ? (CW 22)
Activities
- Meeting w/ Karl: Invitation process w/ and w/o VCS, add source information (host or SVN path+rev #) to file list.
- Created new branch vcsSync.
- FileList refactoring: Extracted all diff related concerns into new class FileListDiff. The invitation processes now only transmit one list of files.
- Store and transmit versioning information in FileList.
Next Steps
- Make peer use the versioning information to check out/update files.
Week ? (CW 23)
Activities
- Synchronization now works if the peer doesn't have Subclipse (optional dependency).
- Factory pattern for VCS adapters: SubclipseAdapter implements VCSAdapter, VCSAdapterFactory provides VCSAdapters.
- Merged FileList refactoring back into trunk.
- Merged changes to trunk (net-refactoring) into vcsSync branch.
Week ? (CW 24)
Activities
- Update files after checkout if necessary.
- Meeting w/ Karl: Add git support. Support core VCS operations in open session (Revert, Update, Commit, Switch).
Next Steps
- Add option for using VCS when synchronizing.