CS logo  Bandwidth:  hi / med / low   

Visit the Surf Shop!   
   Home    Register    CouchSearch!    My Profile    Messages    Groups    Events    Chat77     Info    Login    
Big PictureParticipateMissionStatisticsWikiContact UsAmbassadorsDonateCollectives

Issue tracking

The statements and opinions on this page are solely those of its authors and do not necessarily represent the official position of CouchSurfing International.

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

Contents

Three different aspects of site development

As defined in the Bug reporting guide.

Bug

  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).


Feature

article history edit