[kepler-dev] [Bug 5326] New: 2.2rc2 - upgrade config file bug workaround moves KeplerData/modules to KeplerData/modules.old instead of just configuration file dirs

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: 2.2rc2 - upgrade config file bug workaround moves
                    KeplerData/modules to KeplerData/modules.old instead
                    of just configuration file dirs
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: core
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


The workflow-around for the configuration file bug is to move a user's existing
KeplerData/modules to KeplerData/modules.old during the first launch of 2.2.
However I think we should instead just do something along the lines of moving
each module's configuration dir to a configuration.old. The issue is that more
than just config files reside in KeplerData/modules. E.g. the coreDB and
provenance databases.

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