Project

General

Profile

Bug #5157

Devise approach for when patching should occur when changes occur via the module-manager.

Added by David Welker about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
general
Target version:
Start date:
08/20/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5157

Description

Right now, if you change to a suite through the module manager, it is listed as not being patchable. This might be desirable behavior. Need to devise changes so that patching is possible after changes with the module manager.


Related issues

Blocked by Kepler - Bug #5099: Import Dependent Modules for KAR doesn't workResolved07/21/2010

History

#1 Updated by David Welker about 9 years ago

I have a solution that is good enough for 2.1. The default is that suites are patched. This default can be changed with some work.

Re-targeting any further work on this to 2.2 or later.

#2 Updated by David Welker about 9 years ago

I think our current approach is adequate. The assumption is that when a user selects a patch, they are interested in be prompted for upgrades. If this is not the case, they can uncheck "Automatically check for patches." Given ultimate control in the user over whether patches are checked for or not, having a consistent meaning where suites are checked as long as this check box is checked would be simplest for users to understand.

Closing this bug.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5157

Also available in: Atom PDF