Themes for Team 3.1

Expose
notion of resources that are changed
together as a
logical change.

Could be hooked into validateEdit mechanism, but with a
symbolic comment

A hint
that certain resources should be
checked in together

Local History support for rollback - Investigate local history
synchronize participant example and allow baselining local history by
timestamp with a symbolic name. You could then rollback a refactoring.
This could be coupled with the change set support.

3.1 Development Effort - Milestone 2 (Friday Sept 24th, 2004)

Logical to Physical
[Jean-Michel]

Scope the problem

Send out RFC

Solicit input from
community
and products that have raised
this issue as important for them

Decide on what will be done
for 3.1
[Note: we have scoped the
problem and have decided to split the plan item into two separate
issues. The first will remain as "Support Logical Resources" and the
second will be called "Support mapping between a logical view to
physical files on disk.". For 3.1 we are planning to address the
mapping plan item only.]