[kepler-dev] [Bug 4578] tracking bug for changes to .kepler

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4578

Derik Barseghian <barseghian at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |4785, 4702

--- Comment #9 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2010-02-10 15:38:57 PST ---
After talking w/ Chad and Matt the plan is to mostly leave things as they are.
We just need to add version info to some of the files we're serializing in
KeplerData, and we also decided to change 2.0 to *always* use
.kepler/cache-2.0.0/. I think if we complete bug#4785 and bug#4702, it will
then be safe for 2.0 to delete all of .kepler at will, provided the conversions
have run. Otherwise we should change the build system to not delete all of
.kepler during ant clean-all.

Matt reminded me modules are currently supposed to keep track of their own
versioning. So devs, if you think at some point we'll want to know the version
of serialized data in KeplerData/modules/[module-name]/, you probably want to
be writing that into the files, into a text file, or storing the data in a
versioned directory, etc. I've looked through my wrp ~/KeplerData, and the only
things I see as candidates for needing version info are the coreDB,
core/configuration.xml and provenanceDB. I'll look into these.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.