Hey,
So I looked into this, and we bumped our requirement to Django 1.3.x back
in the 1.6 betas. So 1.6.0 and every release since has had a = 1.3 (and
later 1.3.1 due to security fixes) dependency.
It was the RB 1.5 releases that supported Django 1.2.
In general, every major release of Review
On 27 February 2012 10:53, Christian Hammond chip...@chipx86.com wrote:
Tonight we pushed out releases for Review Board 1.6.4 and RBTools 0.4.0.
There's a lot in each release, so it's worth reading the release notes and
news posts.
RBTools:
On Tue, Feb 28, 2012 at 12:47 AM, adam.coll...@gmail.com
adam.coll...@gmail.com wrote:
On 27 February 2012 10:53, Christian Hammond chip...@chipx86.com wrote:
Tonight we pushed out releases for Review Board 1.6.4 and RBTools 0.4.0.
There's a lot in each release, so it's worth reading the
On Tue, Feb 28, 2012 at 1:03 AM, Christian Hammond chip...@chipx86.comwrote:
On Tue, Feb 28, 2012 at 12:47 AM, adam.coll...@gmail.com
adam.coll...@gmail.com wrote:
On 27 February 2012 10:53, Christian Hammond chip...@chipx86.com wrote:
Tonight we pushed out releases for Review Board 1.6.4
On Tue, 2012-02-28 at 00:24 -0800, Christian Hammond wrote:
Hey,
So I looked into this, and we bumped our requirement to Django 1.3.x
back in the 1.6 betas. So 1.6.0 and every release since has had a =
1.3 (and later 1.3.1 due to security fixes) dependency.
It was the RB 1.5 releases that
Can you tell me which dashboard columns you use?
Christian
On Feb 27, 2012, at 3:34, daniel.j.la...@googlemail.com
daniel.j.la...@googlemail.com wrote:
I just tried to upgrade and i got the 500 something broke error.
I got sent an email trace of the problem - have I done something
Hi Stephen,
It's possible it runs with 1.2.x, but there is absolutely no testing of
this on our end anymore. 1.3 is compatible with 1.2.x, but I understand you
have certain guidelines to work with.
This is a difficult issue, but we basically can't stand still on our end.
It was a mistake for us
On Mon, 2012-02-27 at 11:05 -0800, Christian Hammond wrote:
Hi Stephen,
It's possible it runs with 1.2.x, but there is absolutely no testing
of this on our end anymore. 1.3 is compatible with 1.2.x, but I
understand you have certain guidelines to work with.
This is a difficult issue, but
