Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#101 closed task (complete)

comment keyword to identify revisit points

Reported by: jinmei Owned by: shane
Priority: very low Milestone: Sprint-20110531
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 1.0 Add Hours to Ticket:
Total Hours: Internal?: no

Description

(A year2 fodder, and this is actually not software bug or feature extension, but a matter of style guideline)

We often leave comments including "XXX", "TODO", etc, to indicate the relevant code fragment has a potential problem or needs to be revisited by the release time, etc.

Right now, different developers use different keywords, but it's better to have a consistent style project-wide.

(see also ticket #96)

(tentatively assigning it to Shane as the project manager)

Subtickets

Change History (5)

comment:1 Changed 10 years ago by shane

  • Milestone changed from 01. Running, non-functional authoritative-only server to feature backlog item

comment:2 Changed 9 years ago by stephen

  • Milestone feature backlog item deleted

Milestone feature backlog item deleted

comment:3 Changed 9 years ago by shane

  • billable set to 0
  • Internal? unset
  • Milestone set to Sprint-20110405

comment:4 Changed 9 years ago by shane

  • Defect Severity set to N/A
  • Priority changed from minor to trivial
  • Resolution set to complete
  • Status changed from new to closed
  • Sub-Project set to Core
  • Type changed from enhancement to task

Based on the current code base, TODO is heavily preferred. I've updated the CodingGuidelines to reflect this.

comment:5 Changed 9 years ago by shane

  • Estimated Difficulty changed from 0.0 to 1
Note: See TracTickets for help on using tickets.