> You'll still want the module. I think the best plan of action is to create a simple Python package that ships that with an entrypoint, and just update the Tool entry in > the database to point to that one. That'll help keep that under your control in a more maintainable way. I can point you to what to do for that if it helps.
Yeah, that'll be the best way for review board as project/product as well. > Best option is to get django-evolution 0.6.9 and try an upgrade with that. Will do. > also have to strongly recommend you get a more recent 1.7.x. Preferable 1.7.18. 1.7.6 is almost a year old now True. I had wanted to upgrade in March this year. But then I got distracted to other commitments, such as developing a internal git web, gitolite stuff, and I had a baby...I just came back from paternity leave two weeks ago so I thought I should finish what I left over in March knowing that review board just released 1.7.18:) I plan to upgrade to latest after Christmas:) On Saturday, November 9, 2013 1:28:13 PM UTC-8, Christian Hammond wrote: > > Hey, > > Yeah, it's probably best if we stop shipping that. It doesn't get any > testing. (There's a couple other legacy ones in there we might want to get > rid of). > > You'll still want the module. I think the best plan of action is to create > a simple Python package that ships that with an entrypoint, and just update > the Tool entry in the database to point to that one. That'll help keep that > under your control in a more maintainable way. I can point you to what to > do for that if it helps. > > Going back to the evolutions, running --hint --execute is dangerous. It > will cause further problems down the road, since the proper evolution state > won't be stored. > > Best option is to get django-evolution 0.6.9 and try an upgrade with that. > We've been shipping that as a requirement for a while, since previous > versions have some major issues in certain scenarios, which cause the > problems you're seeing. If upgrading your 1.6.x database to that doesn't > fix anything, there are a couple steps I can walk you through to get that > back into a working state (basically clearing some garbage state stored > from the failed upgrade). > > I also have to strongly recommend you get a more recent 1.7.x. Preferable > 1.7.18. 1.7.6 is almost a year old now, and we've fixed many very important > bugs like this, plus some large security vulnerabilities, browse > compatibility issues, and performance issues since that release. > > Christian > > -- > Christian Hammond - [email protected] <javascript:> > Review Board - http://www.reviewboard.org > Beanbag, Inc. - http://www.beanbaginc.com > > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
