Project

General

Profile

Feature #3288

Update feature in AF3

Added by Anonymous over 2 years ago. Updated 7 months ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
Start date:
02/26/2018
Due date:
% Done:

0%

Estimated time:

Description

The user should download AF3 every time (s)he wants to use the latest version. We should have update feature.


Related issues

Related to Change Request #3386: Add timestamp to RCP "about" dialogRejected04/18/2018

History

#1 Updated by Anonymous over 2 years ago

  • Subject changed from Auto update of AF3 to Update feature in AF3

#2 Updated by Simon Barner over 2 years ago

We used to have such a feature in AF3/DREAMS.

As far as I remember, the update site is already build on Jenkins, and all that needs to be done is:
  • Deploy update during "rollout" phase on Jenkins
  • Enhance RCP application with update feature. This requires some additional dependencies and some code, but it could be even simpler in this case since the download does not have to be password protected.

See: https://jenkins.fortiss.org/view/AF3-DREAMS/job/af3-phoenix-dreams-rollout-aggregation/configure

Things to improve:
  • Organize update site in such a way that also older version of AF3 are collected there. The "rollout" job in AF3/DREAMS simply overwrote the previous update site.

#3 Updated by Anonymous over 2 years ago

  • Target version changed from AF3 2.13 RC1 (Feature Freeze) to AF3 2.14 RC1 (Feature Freeze)

#4 Updated by Alexander Diewald over 2 years ago

#5 Updated by Johannes Eder over 1 year ago

  • Target version changed from AF3 2.14 RC1 (Feature Freeze) to Backlog

#6 Updated by Johannes Eder 7 months ago

  • Status changed from New to Feedback
  • Assignee changed from Anonymous to Simon Barner

@Simon: Do you think we should keep that issue? I think it would be a relevant feature, however I am not sure if its is doable in the next few months.

#7 Updated by Simon Barner 7 months ago

  • Status changed from Feedback to New
  • Priority changed from Normal to Low

Let's keep this in backlog (with low priority).

We should reconsider this in the light of the feature-driven Git workflow and the fact that our continuous integration has moved to Gitlab, too ("eat our own SW development process DF").

Also available in: Atom PDF