Opened 8 years ago

Closed 8 years ago

#1873 closed task (complete)

Requirements and design for msgq(-ng)

Reported by: jelte Owned by: UnAssigned
Priority: medium Milestone: Sprint-20120515
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 8 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by vorner)

The goal is to list what we need the msgq to perform and hint how that could be
done. This is somewhat requirements+design mix in short processing, but it is
needed for discussion before the F2F. Also, there don't need to be too much
detailed requirements, as this is not user-facing feature.


Change History (3)

comment:1 Changed 8 years ago by vorner

  • Description modified (diff)
  • Owner set to vorner
  • Status changed from new to accepted
  • Summary changed from designing msgq changes to Requirements and design for msgq(-ng)

comment:2 Changed 8 years ago by vorner

  • Owner changed from vorner to UnAssigned
  • Status changed from accepted to reviewing

The thoughts are on address Hopefully this is enough to have a nice and fruitful discussin on the F2F.

comment:3 Changed 8 years ago by vorner

  • Resolution set to complete
  • Status changed from reviewing to closed

We talked about it during the F2F and some tasks based on it are being created. So I'm closing the task.

Note: See TracTickets for help on using tickets.