I'd say back up the database and site directory. If you have to revert, you
may need to also manually uninstall the latest Djblets and Django packages
and reinstall the old ones, but that should be fine.
In general, an upgrade should be very smooth.
For memcached, 1.6.x has a setting for configuring the memcached URL, but
for 1.5.x, just add the following to your conf/settings_local.py:
CACHE_BACKEND = 'memcached://localhost:11211/'
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Apr 26, 2012 at 1:21 PM, Alfred von Campe <alf...@von-campe.com>wrote:
> On Apr 25, 2012, at 5:50, Christian Hammond wrote:
> Review Board 1.6.6 is out, and adds support for getting GitHub API tokens
> for private repos.
> I'm running ReviewBoard 1.5.4 on Centos 5.8, and would like to upgrade to
> something more recent (i.e., 1.6.6). However, I've only upgraded once
> before and it didn't go so well (Christian, you helped me out back then --
> thanks again!), so I have been reluctant to upgrade. What are the
> recommended steps to take before an upgrade in case you have to back out
> other than backing up your database?
> Also, when I initially configured RB it was for a very small project and I
> didn't configure memcached. Now the server is being used for a lot of
> projects and performance is beginning to suffer. How do I configure RB to
> use memcached after the fact (I've already done a "yum install memcached"
> and a "easy_install python_memcached"). Finally, what does it take to move
> a site to a different server should I decided to take that route?
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at