Hey Christian,
On Sun, Mar 8, 2015 at 3:45 PM, Christian Hammond
wrote:
> This is one advantage for companies with support contracts -- all information
> is in one place, so we can easily look it all up, merge related discussions,
> store additional information on your setup, etc. Plus, we ha
-Original Message-
From: Srinidhi B S
Reply: Srinidhi B S >
Date: March 8, 2015 at 1:52:41 AM
To: Christian Hammond >
Cc: reviewboard@googlegroups.com >
Subject: Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
> Wow! Thanks a lot for the quick respons
Wow! Thanks a lot for the quick response, Christian! Really appreciate it!
On Sun, Mar 8, 2015 at 2:58 PM, Christian Hammond
wrote:
> Okay, I guess I was a bit confused here by which versions you're trying when.
>
> The "Django Evolution is too new" issue would apply if upgrading to a 1.7.x
> re
legroups.com >
Subject: Re: Upgrading from 1.0.6 to 2.0.x - suggestions and recommendations?
> Thank you so much David and Christian for your responses! I was almost
> losing hope once again and hence, didn't check back for the last 4
> days. :)
>
> On Wed, Mar 4, 2015
Thank you so much David and Christian for your responses! I was almost
losing hope once again and hence, didn't check back for the last 4
days. :)
On Wed, Mar 4, 2015 at 8:43 AM, Christian Hammond wrote:
> The problem is that your django_evolution you too new. We didn't have strict
> enough depen
The problem is that your django_evolution you too new. We didn't have
strict enough dependency version range requirements back in 1.7.6, so
you'll run into some of this. You'll need to grab django_evolution 0.6.9 at
the newest.
Christian
On Tuesday, March 3, 2015, David Trowbridge wrote:
> Hi,
Hi,
So I'm by far not an expert on the evolutions, but that change looks like
it's likely to break things pretty badly (in particular, file-attachment
only review requests). Christian, any thoughts on what's causing the errors?
-David
On Fri, Feb 27, 2015 at 7:40 AM Srinidhi B S wrote:
> Hi,
>
Hi,
On Thu, Jan 29, 2015 at 10:39 PM, Srinidhi B S wrote:
> Hello Everyone,
>
> I'm (finally!) preparing to upgrade our very old ReviewBoard instance
> from 1.0.6 to 2.0.12. I've been worried / concerned about the upgrade
> path.
>
> The following are the changes that could not be resolved:
>
Hi,
I tried switching to ReviewBoard 1.7.6 again (easy_install -U
ReviewBoard==1.7.6) and then tried "rb-site upgrade". This time, I get
even more failures:
# rb-site upgrade /path/to/site
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including wa
Hello Everyone,
I'm (finally!) preparing to upgrade our very old ReviewBoard instance
from 1.0.6 to 2.0.12. I've been worried / concerned about the upgrade
path.
Around this time last year, I did attempt an upgrade from 1.0.6
directly to 1.7.6 and things seemed to have worked out fine. But I
coul
10 matches
Mail list logo
