RE: [mylar-dev] Dev-builds for Eclipse 3.2

["Mik Kersten" <beatmik@xxxxxxx>]

Regarding sharing contexts: the format has been very robust to change
because we store the sequence of interaction events, not the actual model,
and this format has not been changed since first created.  So Mylar 2.0 can
happily share contexts with Mylar 0.2 (if you find any users of it, there
was only one ;)  

Regarding the Task List: this is only of concern with manually moving your
.mylar folder between Eclipse versions.  The Mylar 2.0 Task List is not
likely to support being moved back to Mylar 1.0, unless someone provides a
reason compelling enough to justify the work.

Given that, it seems that you should be able to happily use Mylar 2.0Mx?
The only limitation being that if you are on 3.2 it will take longer to get
dev builds.
 
Mik 

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Willian Mitsuda
> Sent: Friday, February 09, 2007 1:13 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Dev-builds for Eclipse 3.2
> 
> On 2/9/07, Mik Kersten <beatmik@xxxxxxx> wrote:
> > What is likely to happen in the 2.0 stream is that we update the
> format, say
> > if Mylar 2.0M3 had improved a Task List and Context Store format in
> the
> > .mylar folder.  When you update to it your data will be automatically
> > migrated as it has been with previous releases.  But this would only
> prevent
> > you from moving from Mylar 2.0 back to Mylar 1.0.x, not from moving
> between
> > Eclipse versions.  I put a note on this at:
> >
> 
> That's the point. On this case I will be tied on Mylar 2.0.
> 
> What I propose then, is to always have a dev-build for 3.2 when such
> thing happens, so I can go back to Eclipse 3.2 if I need, and to be
> able to share my contexts with 3.2 users (if any).
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev