From Fedora Project Wiki
(Created page with '==Trac plugins == trac-xmlrpc-plugin trac-customfieldadmin-plugin trac-mercurial-plugin email2trac trac-ticketdelete-plugin trac-toc-macro trac-monotone-plugin trac-iniadmin-plu...')
 
No edit summary
Line 1: Line 1:
Overview: each of these should have at least a single simple test for success detailed. This will aid with future upgrades by giving us a reference for behavior.
== trac proper ==
FAS auth
===Tickets===
* ticket creation
* ticket resolution
* email notification of ticket changes
===Wiki====
* page creation
* search
* page editing
===Admin===
==Trac plugins ==  
==Trac plugins ==  
trac-xmlrpc-plugin
trac-xmlrpc-plugin

Revision as of 01:36, 14 December 2010

Overview: each of these should have at least a single simple test for success detailed. This will aid with future upgrades by giving us a reference for behavior.

trac proper

FAS auth

Tickets

  • ticket creation
  • ticket resolution
  • email notification of ticket changes

Wiki=

  • page creation
  • search
  • page editing

Admin

Trac plugins

trac-xmlrpc-plugin trac-customfieldadmin-plugin trac-mercurial-plugin email2trac trac-ticketdelete-plugin trac-toc-macro trac-monotone-plugin trac-iniadmin-plugin trac-peerreview-plugin trac-git-plugin trac-webadmin trac-tickettemplate-plugin trac-bazaar-plugin trac-privateticketsplugin

Scripts

put list of scripts that we use to interact with trac


Upgrade process

Is the process merely one of upgrading trac, and everything just works, or must data be munged.


Surrounding things

Upgrading trac is really upgrading the entire hosted platform - which means we should run through things like repo creation script/sops to make sure they are still sane.