Re: Upgrading Review Board 1.7.6 to 2.0.2

Robert, It's easiest (and safest) to develop extensions using a development environment for Review Board rather than a production deploy. We have instructions for creating a dev environment at https://www.reviewboard.org/docs/codebase/dev/getting-started/ -David On Wed, Oct 21, 2015 at 2:09 PM,

Re: Upgrading Review Board 1.7.6 to 2.0.2

David, When doing the extension what would the right file path for this extension and does another file call it or does it need a specific name? -Robert On Tuesday, October 20, 2015 at 2:14:07 PM UTC-6, David Trowbridge wrote: > > Robert, > > You can either do it as part of an extension, or

Re: Upgrading Review Board 1.7.6 to 2.0.2

David, When doing the upgrade from 1.7.6 to 2.0.20 using the easy_install command I received no errors as I previously stated. In order to create the extensions you recommended which utilizes the contrib directory, this was not installed when upgrading review board. Does this directory need to

Re: Upgrading Review Board 1.7.6 to 2.0.2

David, How would I go about doing that? I'm new to python why I went the route that I did. -Robert On Monday, October 19, 2015 at 2:29:03 PM UTC-6, David Trowbridge wrote: > > > On Mon, Oct 19, 2015 at 1:25 PM, Robert Bolen > wrote: > >> 'Mantis User Database' > > > This

Re: Upgrading Review Board 1.7.6 to 2.0.2

Robert, You can either do it as part of an extension, or just using entry points. See https://www.reviewboard.org/docs/manual/2.0/extending/auth-backends/#packaging -David On Tue, Oct 20, 2015 at 9:15 AM, Robert Bolen wrote: > David, > > How would I go about doing that?

Re: Upgrading Review Board 1.7.6 to 2.0.2

On Mon, Oct 19, 2015 at 1:25 PM, Robert Bolen wrote: > 'Mantis User Database' This is not part of the upstream Review Board code. It looks like you have some custom modifications that are broken. There's no reason to ship additional authentication backends as a patch to