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

["Mik Kersten" <beatmik@xxxxxxx>]

All current Mylar versions will always have this data no matter.  So while
you are deciding you can happily have both a 3.2 workspace and a 3.3
workspace point at the same .mylar folder (just don't run them at the same
time.

For versions that have reached their end-of-life we always specify the
update path so that the contents of the .mylar folder are updated.  This is
listed in the "Update notes" on top of the New & Noteworthy:

http://eclipse.org/mylar/doc/new.php

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:

http://wiki.eclipse.org/index.php/Mylar_FAQ#Releases_and_development_builds

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Willian Mitsuda
> Sent: Friday, February 09, 2007 12:38 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Dev-builds for Eclipse 3.2
> 
> Mik,
> 
> On 2/8/07, Mik Kersten <beatmik@xxxxxxx> wrote:
> > Willian: after M5 goes out it would be good if you could post back on
> > whether you could move to it or not.
> 
> I intend to, but I'll still use 3.2 and there is a possibility to
> other people who work with me to use 3.2 too.
> 
> My main concerns are:
> 
> 1 - Task context format changes - If I'm using mylar for 3.3, I want
> to be able to read attached contexts produced by 3.2, and to produce
> contexts that will be read by 3.2 users.
> 
> 2 - Context store changes - Perhaps due to some bug on 3.3 I could be
> forced to go back to 3.2 (using the same workspace). On this case I'm
> worried about what could happen to my context store.
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev