This project is read-only.

Install & Update Feature Team (1.5)

Topics: Announcements, Core
Mar 14, 2012 at 11:59 PM

This is the thread for the install and update feature team, where one can volunteer to do work and discuss design.

Strawman design proposal:

  • Core updates
    Enables update of Orchard itself, without complicated manual upgrades. Design TBD, but Sébastien has some ideas.
  • filtering gallery on version
    This requires the gallery feed to expose Orchard compatibility information from the module/theme manifest, and the Orchard.Gallery module to use this information to filter the list. TBD: should versions allow for intervals or only minimum version like today? 
  • automatic dependency downloading
    When a module is downloaded, its dependencies are also downloaded if not already available. Feature activation only for the requested module is shown, and any dependency feature will be enabled as needed by dependency order. Dependency recursion is necessary if C depends on B which depends on A. 
  • gallery: not having to reset images for each new version, better mapping to the manifest
    That's purely in the gallery code. When uploading a new version, the descriptions and images should be taken from the previous version as the default values (instead of manifest and nothing like today) 
  • Mercurial module updates (this one is lower priority although high on cool factor)
    If time permits, this very cool feature would enable the gallery page for a module or theme to point to a Mercurial repository instead of giving a binary package to download. A module author would not have to take advantage of this feature, but if he does, publishing a new version of his package would just consist in merging into the branch that has been configured on the gallery. A user of the module would see a new version available, and if he decides to take it, Orchard would use the Mercurial protocol to update its clone to the new version. Some constraints on Hg protocol may require to tunnel through the gallery server.


Mar 15, 2012 at 8:45 PM

I think the priority with modules should now be to provide a flawless, bullet-proof management of modules: that means, let module authors specify (with open or closed intervals) which Orchard version their module works and which dependencies (also with versions) it requires. Filtering in the Gallery would be a nice feature, but IMO more important is to prevent the installation of incompatible modules (which would still be possible if one installs a module through some other channel than the Gallery); much like how with 1.4 modules with missing dependencies can't be enabled.

Mar 20, 2012 at 10:55 PM

+1 for version check of module dependencies.

Apr 27, 2012 at 1:29 AM

Please start using for task management on this feature team.


May 9, 2012 at 3:04 AM

Feature Team Leaders, please join us tomorrow at 1PM Pacific Time for a status report at (Lync client required). If you can't join us, please leave us a note here giving status before the meeting.