Opened 11 years ago

Closed 6 months ago

#767 closed defect (fixed)

First point under "do this to upgrade" in release notes is something to do after upgrading

Reported by: Mike Linksvayer Owned by:
Priority: major Milestone:
Component: documentation Keywords:
Cc: Mike Linksvayer Parent Tickets:


There seems to be a missing step:

Do this to upgrade

  1. Make sure to run ./bin/python develop --upgrade && ./bin/gmg dbupdate after upgrading.

You have to search back to 0.3.2 to find actual (but poorly formatted) instructions. This is a pain for someone upgrading for the first time, especially not knowing what they're doing. I forget everything between releases, so it is the first time everytime.

Change History (3)

comment:1 by Christopher Allan Webber, 11 years ago

Status: newaccepted

I agree that the current upgrade steps are not ideal... but not totally sure what would be best to improve these instructions. Maybe linking to the release notes?

A "make upgrade" would be better, and that exists in the pyconfigure branch, but it's not the "official method of doing things" until #755 is merged.

comment:2 by Christopher Allan Webber, 10 years ago

Cc: Mike Linksvayer added

Well, #755 is merged long ago, and the ./configure && make stuff got overhauled very recently even, but I think that a make upgrade may not be the right solution. For one thing, we should be getting to the point where (not all) users are deploying from git at all, and usually running from a system packaged solution.

That still leaves how to deal with database migrations and any intermediary steps. But that would be a large step forward.

comment:3 by Ben Sturmfels, 6 months ago

Resolution: fixed
Status: acceptedclosed

Closing. While we haven't yet moved to a non-git deployment approach, the release notes and upgrading instructions are at least consistent and well-tested.

Note: See TracTickets for help on using tickets.