Task #3870 (closed)
Opened 13 years ago
Closed 7 years ago
Automation of client update
| Reported by: | saloynton | Owned by: | rkferguson |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Version: | OMERO-5.2.0 |
| Keywords: | n.a. | Cc: | jamoore, jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by saloynton)
Following the ongoing feedback both locally and externally the automation of the client updates is a heavily desired feature.
To determine priority for next release.
Change History (6)
comment:1 Changed 13 years ago by saloynton
- Milestone set to OMERO-Beta4.3
comment:2 Changed 13 years ago by saloynton
- Description modified (diff)
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:3 Changed 13 years ago by saloynton
comment:4 Changed 13 years ago by saloynton
- Description modified (diff)
- Summary changed from Prototype web start to Automation of client update
comment:5 Changed 11 years ago by jburel
- Owner changed from saloynton to rkferguson
comment:6 Changed 7 years ago by jamoore
- Resolution set to wontfix
- Status changed from new to closed
- Version set to OMERO-5.2.0
Will be solved by migration to web
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
With the feedback from Norwich the ability of automated updates for the client was also one of the frequently requested areas of functionality. This might need to be taken into consideration for the next release.