[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

Matt Jones <jones at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jones at nceas.ucsb.edu

--- Comment #5 from Matt Jones <jones at nceas.ucsb.edu> 2010-08-09 14:01:56 PDT ---
I think we're all in agreement about wanting installers most of the time. 
However, in the case of 2.1, the changes are minimal and focused on just
delivering the needed changes to support the new reposting modules.  So, if
someone chooses to install the reporting module (via the module manager), they
will automatically also get the 2.1 upgrades needed to support reporting.  The
next major release would be 2.2, and we would plan on building an installer for
that.  Our hope was that by 2.2 we could fully automate the process of building
the installers so that this would no longer be an issue (because building the
installer would be simple).

One thing we might consider is to have the module manager check for updates to
their installed modules and prompt users to tell them that upgrades are
available.  This would help to allow quick updates for users that already have
Kepler 2.0 installed so they don't have to get the whole installer when just a
couple of modules have changed.

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