#10102 closed task (fixed)
Mention hotcopy in UPGRADE document
Reported by: | Thijs Triemstra | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.5 |
Component: | admin/console | Version: | 0.12-stable |
Severity: | minor | Keywords: | |
Cc: | Thijs Triemstra | Branch: | |
Release Notes: |
UPGRADE document has a step to backup the environment. |
||
API Changes: | |||
Internal Changes: |
Description
The trunk/UPGRADE document explains the upgrade process but doesn't reference the hotcopy
command as a way to do a backup of the environment (including the database) before doing the upgrade.
Attachments (0)
Change History (6)
comment:1 by , 12 years ago
Milestone: | → undecided |
---|
comment:4 by , 10 years ago
Milestone: | undecided → 1.0.4 |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:5 by , 10 years ago
Release Notes: | modified (diff) |
---|
I'll add as the first step Backup the environment, with a short description of how to do that using hotcopy
.
comment:6 by , 10 years ago
Milestone: | 1.0.4 → 1.0.5 |
---|
comment:7 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Wiki edited in TracUpgrade@113 and TracUpgrade@114.
trunk/UPGRADE revised in [13733:13734].
It's not efficient to duplicate the documentation, so if we can find a solution to that issue it will reduce the amount of work, particularly in preparing the release: gmessage:trac-dev:oMJ42ETozL0/slolTrwJL1YJ.
All the tickets for {20} from last year have probably been seen multiple times by now, yet are still to be triaged…