[kepler-dev] [Bug 5126] Determine whether we need to make installers for all minor releases

[bugzilla-daemon at ecoinformatics.org]

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

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #7 from Christopher Brooks <cxh at eecs.berkeley.edu> 2010-08-11 17:43:44 PDT ---
Thanks, I'm closing this one.

We run the risk of users not having the most recent version and
of confusing the user as to what version they are running, but
since 2.1 is really only necessary for the reporting module, and
2.2 should be out shortly, then we should be ok.

I see these usage scenarios:
1) User downloads 2.0 and uses it.
2) User downloads 2.0, gets the reporting module and gets 2.1.

A better usage scenario would be:
1) User downloads 2.0, we automatically check to see if there is an update.
If there is, we suggest that the user install 2.1.
2) User downloads 2.0, if they have want the reporting module,
then they are forced to upgrade to 2.1.

The advantage is that it means that most users will be using
the most recent version.

However, we can live with what we have today for the short term.

We should watch out for the 2.0 vs. 2.1 split in support email though.

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