Issue tracking

From the CouchSurfing Wiki, an informal workspace which anyone can edit.

Issue tracking is very important. It's all about communication.

• Bug reporting guide for developers and non-developers.
• http://bugs.couchsurfing.com, you can create your own account, just ask Kasper or Anu for more permissions.

Contents 1 Three different aspects of site development 1.1 Bug 1.2 Usability issue 1.3 Feature

Three different aspects of site development

As defined in the Bug reporting guide.

Bug

• CS Group: Cockroach
• Steps

1. check Bug Tracker (BT) or Cockroach group for existing bugs
2. If a bug found in the group is not in BT already, report it there AND tell "thanks for reporting" or something similar in the Cockroach group
3. Reassign bug to yourself in BT so other developers know you're working on it
4. Start working on the bug on your local copy of CS server
5. Try to make sure the bug has indeed been fixed before committing it to SVN
6. Commit your changes to SVN
7. All SVN commit notifications are sent to SVN commits mailing list. Casey / Anu / Ondrej / Matrixpoint can upload fixed file(s) to live site (note: beta server should be up soon!)
8. Edit bug status in BT: resolved / fixed
9. Once your fixes have been uploaded onto live site, report the bug fixed in the Cockroach group thread where it was first reported (in case there is one).

Usability issue

• Usability issues are bugs as well, though some are not located in the code but need to be tackled by Admins or Group leaders (e.g. group names).

• Usability resources:
  • User Interface Engineering

Feature

• CS group : Brainstorm
• Site improvement at the Wiki
• Feature to implementation process is pretty much ad-hoc for the moment - pending CS organizational structure finalization