Christian Hammond wrote:
...A couple important notes:
1) I would strongly recommend that, if you want to test new versions,
that you do it on a non-production system, such as your own machine or
on a VM. You can always copy over your database if you need to. That's
the best way of making sure
On Mon, Jul 18, 2011 at 08:31, jh5774@samsung.com
wrote:
> Please, is anyone help me from this hell?
Hmmm, it's very easy to install 2 differents versions with virtualenv:
create a virtualenv for each. But I don't know if it's work well with
Apache.
--
Sebastien Douche
Twitter : @sdouche
Well, Good Afternoon,
I have two news. Good and bad.
good news is, I succeed to downgrade reviewboard's version to 1.5.5.
** snake's leg.
: easy_install -U ReviewBoard=1.5.5 is not working. But fortunately,
latest official release version is 1.5.5. So, I just type like that =>
easy_install -U Re
Thank you for your kindness.
This is response for your question:
/var/www/dev_rb
/var/www/second_dev_rb
two reviewboards have different databases.
And, I think it's python path is main issue, too.
But I don't know solutions how to set these path.
Thank you for your response, again.
Have a ni
Hi,
Since Review Board is a Python module, and is installed to the system module
directory, the newest version will always be used by default.
To get back to a working 1.5.5, you can locate the ReviewBoard-1.6rc1*.egg
directory and delete it. Then re-register 1.5.5 through easy_install by
doing:
Well, Good afternoon, gentlemans.
We using reviewboard 1.5.5 in our development team with wrapping some
functions.
Now, I heard that new version -1.6rc1 is released.
We decide that we test 1.6rc in our test server with 1.5.5.
But I have some problems when I upgrade our dev_test rb_server to
1.
