Bug#753910: [PATCH] Add support for showing Debci test failures as an action item. Closes: #753910
Control: clone -1 -2
Control: retitle -2 [docs] Add a tutorial for common cases: new panel, new action item, new link, downloading data
Control: tags -2 -patch
On Mon, 07 Jul 2014, Andrew Starr-Bochicchio wrote:
> Thanks for the feedback. Just trying to get a feel for the code base.
> It might be nice if the docs included a quick tutorial on the common
> task of adding a new panel or action item. It would give people a
> quick way in to contributing.
Right! Cloning this into a new ticket.
> > On Sun, 06 Jul 2014, Andrew Starr-Bochicchio wrote:
> >> +@python_2_unicode_compatible
> >> +class DebciStatus(models.Model):
> >> + """
> >> + Model for debci status of packages.
> >> + """
> >> + package = models.OneToOneField(PackageName, related_name='debci_status')
> >> + status = JSONField()
> >
> > Please don't add a new model for this. Rather use a new "key" in
> > PackageExtractedInfo.
> >
> > PackageExtractedInfo model should probably be renamed into something else
> > but it's the better place to store this as we can then query most of the
> > relevant information for a single package in a single query...
>
> Right. After I sent this off, I wondered if it needs to store this
> information at all. Is enough to just store the information in the
> action item?
Possibly, yes. It really depends on whether you expect other parts of the
package tracker to build upon this information or not.
But we can always move it to a more appropriate place later on if we
we have something that needs this information.
Thanks,
--
Raphaël Hertzog ◈ Debian Developer
Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
Reply to: