Community
Participate
Working Groups
There is a significant effort underway to improve the foundations of the Mylyn Reviews project. This involves re-designing key components and implementing adopting more EMF-centric approaches. There are at least three main themes, all of which interrelate: #Implementing Common Edit Framework based on EMF Edit #Implementing a Remote API #Implementing a Synchronization/Concurrency Support Many of these issues have been discussed in detail in other related bugs, e.g. bug 399700 bug 395646 bug 394020 bug 384770, but as they many of the issues overlap, it probably makes sense to discuss the major design issues in a single place. We'll be tracking the resulting high level design at http://wiki.eclipse.org/Mylyn/Reviews/Reviews_Convergence_2013
Thanks for driving this. Let's have the initial discussion on the call next Wednesday.
As a side note. We are planning to use the resulting design as a base to migrate R4E too, so that R4E extends the gerrit functionality and provides additional features that do not exist in Gerrit. So we definitively want to be involved in the discussion. From our persective what's needed is: 1 - A common way to edit the Review and Artifacts model properties (EMF Edit) 2 - A generic remote API that will tie the Reviews EMF model with Backends (such as the Gerrit Server) and will transparently be used to Store and Retrieve Information from said backend. The API could then be implemented for specific backends (e.g. Gerrit). 3 - A way to cache and persist the Review data locally (ideally by serializing/deserializing the EMF Review model data) and to synchronize/rebase/merge that local data with the Remote data from the backend. As you can see we are pretty much aligned in what needs to be done.
See bug 400356 comment 4 for current state of play.
We can close this now, 2.0.0 has been released.
