Actions
Task #5889
openAdd upgrade information to the docs
Status:
NEW
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Quarter:
Q4-2021
Description
The installer supports upgrading (see https://pulp.plan.io/issues/5884 ) we just need to document it for the user.
Updated by bmbouter about 5 years ago
- Tracker changed from Task to Issue
- Severity set to 2. Medium
- Triaged set to No
Updated by fao89 about 5 years ago
- Tracker changed from Issue to Task
- % Done set to 0
Updated by mdepaulo@redhat.com about 5 years ago
Per convo during bug triage:
Does this correspond to micro update instructions? Or major/minor version upgrades?
Installer micro-updates: https://pulp.plan.io/issues/5891
Installer upgrades: https://pulp.plan.io/issues/5884
For now, the logic would be the same between the 2. But at some point, more steps would be involved in upgrades.
Also, what Gluster does for example is put the update/upgrade instructions in their release notes.
Possibly because they feel it makes them more likely to be followed, possibly because it makes them easier to update after release.
Updated by ipanova@redhat.com over 3 years ago
- Quarter changed from Q2-2021 to Q3-2021
Updated by ttereshc over 3 years ago
- Category set to Installer - Moved to GitHub issues
Updated by ipanova@redhat.com about 3 years ago
- Quarter changed from Q3-2021 to Q4-2021
Actions