A newer version of FogBugz is available. (Dismiss this message)
What procedures do you follow?
|
4
1
|
|
||
|
|
|
3
|
I have a link on my FogBugz server with the URL of the FogCreek download page, so that I can jump directly to it without having to re-enter my order number and e-mail address. This helps to easily download the latest version. FogBugz release are generally such good quality that I can just upgrade my production instance without fear of breaking anything. The only issue I've had in the past with an upgrade was the upgrade to FogBugz 7 (due to stuff around the switch to ASP.Net). Generally even major upgrades take no longer than a 1/2 hour to implement, and have caused no harm in production. Recommended steps, then (for a patch): 1. Notify users that FogBugz will be down for up to 30 minutes (to be safe) 2. Download the latest release off of the web site 3. Back up FB database 4. Run installer 5. Verify that FogBugz runs 6. Notify users that FogBugz is back up Thankfully FogBugz stores the previous release server software in a directory that is a sibling to the install directory, making it easier to restore the previous version in the unlikely event that this is required. |
||
|
|
|
1
|
That should be all you need to do! |
||
|
|
