[kepler-dev] [Bug 5161] New: can't always use Module Manager to change to an older patch of a suite

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: can't always use Module Manager to change to an older
                    patch of a suite
           Product: Kepler
           Version: 2.0.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: interface
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


If a module is published
and a patched version of this module is published
and the user has downloaded both
and the user uses the MM to change to the original version of the module
Kepler will restart and automatically use the newest patch of the module that's
available on the local system, with no notice.

I would expect a user would be able to intentionally change to the old patch,
especially since it's visible in the MM's gui.
Even if 'Automatically download new patches' is left on, they should get the
prompt for an update on restart, I would think.

Is this a known issue, compromise, or intentional choice the MM is currently
making? It's not strictly necessary for 2.1, because the Import Module
Dependencies feature does allow this (and that's when it's *really* necessary).
Also since the IMD feature can prompt a user to do this (restart into an older
patch), I think a user would think they could also use the MM to do it.

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