*** P.S. I believe that in terms of user experience the Platform there
will be a big cost with the current approach of forcing each team
provider to implement its own silo of synchronization, change sets
support, and the corresponding UI. I just don’t buy the current story
that the Team user experience should only work well for developers
having one source repository, because a significant portion of
developers check out sources for both their project and the frameworks
that they build on. Not having change sets be a part of platform is
part of the problem, but symptoms of this show up on other reports as
well:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=146917#c9
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=89806
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=138583
I realize that Platform/Team may not have the resource to do this, but
I’m wondering if it should at least be discussed as an issue in case
others in the community are willing to help improve those key parts of
the Team API.
