Bug 37307 – ini variable for apps that will never see a new UCS release

Bug 37307 - ini variable for apps that will never see a new UCS release


Summary:	ini variable for apps that will never see a new UCS release

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-12-11 17:27 CET by Dirk Wiesenthal
Modified:	2020-07-03 20:55 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

2014-12-11 17:27:45 CET

When releasing a new minor or major version of UCS, this update is blocked for users with apps not (yet) present in this UCS' App Center.

Some apps will never be made available for this new UCS version. A variable in the ini file may indicate that waiting for that app is fruitless and the user has to stick to the old version. The updater module may suggest to "search for alternative apps".

AvailableOnNextRelease=False

or even

ReplacedByOnNextRelease=anotherappid

in which case the suggestion may be more specific.

Comment 1 Nico Gulden

2015-01-29 09:00:58 CET

Both variables sound valueable. As soon as the user receives a note that an app will prevent the upgrade and suggests to look for an alternative, we should, if possible, recommend such an alternative.

Comment 2 Ingo Steuwer

2020-07-03 20:55:01 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.