Ticket #1666 (closed feature: moved)

Opened 6 years ago

Last modified 5 years ago

Enhance update mechanisms

Reported by: bdezonia Owned by: dscho
Priority: major Milestone: imagej2-b8-analysis
Component: Community Version:
Severity: serious Keywords:
Cc: Blocked By: #1738, #1739, #1740
Blocking: #1664

Description (last modified by curtis) (diff)

We may want to support multiple "update channels". In the process we may need to add the capability to Fiji/ImageJ2 to choose to downgrade a version.

Change History

comment:1 Changed 6 years ago by curtis

  • Owner changed from curtis to dscho
  • Status changed from new to assigned
  • Type changed from defect to feature
  • Description modified (diff)

Update channels

The current Updater architecture does support multiple update sites, with some able to "shadow" files from others. So it is certainly possible to have e.g. a "stable" and "experimental" update sites for users to overlay.

The main issue is that right now the Updater UI could make this much easier. We could have built-in lists of update sites, with a clear order of priority (so that users cannot too-easily accidentally shadow things in the wrong order). We could explicitly display an update site as an "experimental" version of another update site.

Downgrades

Adding support for downgrade is a separate issue, but would also be very doable. All the information about old versions exists in the db.xml.gz on the server, and those old versions are still accessible. But there is not yet a defined API for explicitly downgrading to an old version. So we would need such an API, as well as enhancements to the command line and GUI updaters to support it.

I have changed this ticket to a "feature" since it is a high-level goal, and so that we can add subtickets covering aspects of this work in more detail.

comment:2 Changed 6 years ago by dscho

  • Blocked By 1738 added

comment:3 Changed 6 years ago by dscho

  • Blocked By 1739 added

comment:4 Changed 6 years ago by dscho

  • Blocked By 1740 added

comment:5 Changed 5 years ago by curtis

  • Status changed from assigned to closed
  • Resolution set to moved

Regarding update channels, the multiple update sites are enough for now.

Regarding downgrades: see  https://github.com/imagej/imagej/issues/23

Note: See TracTickets for help on using tickets.