#280: Move multiproduct.model.ModelBase to dashboard plugin
---------------------------+------------------------------------
Reporter: olemis | Owner: franco
Type: enhancement | Status: review
Priority: trivial | Milestone:
Component: multiproduct | Version:
Resolution: | Keywords: database model testing
---------------------------+------------------------------------
Changes (by franco):
* status: accepted => review
Comment:
Until further discussion takes place, and it get to be finally decided if
creating the new bloodhound_core directory, I have submitted two new
revisions:
[https://bitbucket.org/jose_angel_franco/bloodhound-
dashboard/commits/9e3ae4c54bb8b93844088559686804a6]
[https://bitbucket.org/jose_angel_franco/bloodhound_multiproduct/commits/d39109663a717d7743109507fb22d335]
moving ModelBase to model.py as accurately observed by rjollos.
I pass the solution to revision state, you can grab the diffs here:
[https://bitbucket.org/jose_angel_franco/bloodhound_multiproduct/compare/t280_move_modelbase_to_dashboard..default]
[https://bitbucket.org/jose_angel_franco/bloodhound-
dashboard/compare/t280_move_modelbase_to_dashboard..default]
Best regards,
Franco
Best regards,
Franco.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/280#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
