From Fedora Project Wiki
Iaslanidis (talk | contribs) (Reformatted the page a little bit. Added a few more things to test.) |
|||
| Line 5: | Line 5: | ||
===Tickets=== | ===Tickets=== | ||
* | * Ticket creation | ||
* ticket | * Ticket changes | ||
* | * Ticket resolution | ||
* Add attachment to ticket | |||
* Email notification of ticket changes | |||
===Wiki=== | ===Wiki=== | ||
* | * Page creation | ||
* | * Page editing | ||
* | * Page deletion | ||
* Page version deletion | |||
* Add attachment | |||
* Delete attachment | |||
* Overwrite attachment | |||
* Macros | |||
* Search and queries (stress test advised) | |||
===Admin=== | ===Admin=== | ||
==Trac plugins == | ==Trac plugins == | ||
trac-xmlrpc-plugin | * trac-xmlrpc-plugin | ||
trac-customfieldadmin-plugin | * trac-customfieldadmin-plugin | ||
trac-mercurial-plugin | * trac-mercurial-plugin | ||
email2trac | * email2trac | ||
trac-ticketdelete-plugin | * trac-ticketdelete-plugin | ||
trac-toc-macro | * trac-toc-macro | ||
trac-monotone-plugin | * trac-monotone-plugin | ||
trac-iniadmin-plugin | * trac-iniadmin-plugin | ||
trac-peerreview-plugin | * trac-peerreview-plugin | ||
trac-git-plugin | * trac-git-plugin | ||
trac-webadmin | * trac-webadmin | ||
trac-tickettemplate-plugin | * trac-tickettemplate-plugin | ||
trac-bazaar-plugin | * trac-bazaar-plugin | ||
trac-privateticketsplugin | * trac-privateticketsplugin | ||
== Scripts == | == Scripts == | ||
Here is the list of scripts that we use to interact with trac: | |||
TODO | |||
| Line 41: | Line 51: | ||
Is the process merely one of upgrading trac, and everything just works, or must data be munged. | Is the process merely one of upgrading trac, and everything just works, or must data be munged. | ||
TODO | |||
== Surrounding things == | == 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. | 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. | ||
Revision as of 19:55, 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 changes
- Ticket resolution
- Add attachment to ticket
- Email notification of ticket changes
Wiki
- Page creation
- Page editing
- Page deletion
- Page version deletion
- Add attachment
- Delete attachment
- Overwrite attachment
- Macros
- Search and queries (stress test advised)
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
Here is the list of scripts that we use to interact with trac:
TODO
Upgrade process
Is the process merely one of upgrading trac, and everything just works, or must data be munged.
TODO
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.