Comment 8 for bug 49698

Andrea, you rock!

I think you should do this bug in smaller steps. This is a multi-branch effort that will require some agreement with other developers about how to precede. This is one of the reason comments are not added yet.

I have some familiarity with this issue. The expectation is that these should behave like bug comments. To do this several branches need to be landed in a specific order. You should discuss each phase with a launchpad developer before you start hacking. Present an outline of what you want to do. the developer can show you code you can reuse.

1. Schema changes
    This adds comment storage or allow blueprint comments to be shared with bugs
    This requires a review by sabdfl after it has been removed by an engineer
    The branch will be landed to db-devel
2. Interface-model changes
    Create the definition and implementation of blueprint comments
    Consider extracting bug comment code to a mixin so that common code can be shared
    This will add doctests for the new object and maybe some unittests to verify they are robust.
3. View changes
    Add the views need to add, view, and edit (yes, let's plan for editing now)
    You may write unittests or doctests to verify the views do as intended
4 template change
    Add real templates and integrate the comments into other pages.
    Expose the behaviour to the world.
    Add a story test to verify that users can get to and from comments.

Ping me if you need my assistance.