Hi Rosie,

We have had a few cases where support customers are getting confused as to whether they should upgrade using the proper way (XML export and import) or by the "quick" way - pointing the new instance at the existing database. In particular, some customers seem confused about when they need to do the intermediate step via 3.7 (only needed for the "quick" way, but some customers think they need to do this for proper way as well).

I think it might need a technical writer's eagle eye over Upgrading JIRA Safely and SQL Scripts for 3.6.x to 3.7 schema upgrade, to make sure that this documentation is as crystal clear as it can be.

While you are there, Jeff has written a page on Making databases read-only for upgrade backups. Could you please add a link to it from the main doco, although some of the initial description in that page - the first four or five sentences about the issues around ensuring a consistent backup by making sure no one is changing the database - should probably go in the main page.

Let me know if you need any help or further info. Thanks.