id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
913,Wiki page states,bgoedel,anybody,We would like to use Trac Wiki pages to write specifications_ for instance detailed design specifications for SW components_ test plans_ etc. There are also a lot of mandatory documents describing the project setup as a Configuration Management Plan_ a Quality Assurance Plan_ a Resource Plan_ etc.\r\n\r\nThe project developing process foresees that each of these documents is reviewed by a defined set of team members. Thus_ each document has a number of states:\r\n\r\n in progress::\r\n The (version of the) document is currently written by the Author.\r\n available for inspection (AFI)::\r\n The document is frozen and reviewed by a pre-defined set of team members. Each reviewer has to write comments about the objections she/he has (we have already a tool for this). The review comments are worked in into a new version of the document which is then in the state\r\n inspected_ updated_ stored (IUS)::\r\n The version of the document that is valid for the project.\r\n outdated::\r\n This version of the document is not valid anymore due to the availability of a newer IUS version of the document.\r\n\r\nFor "living documents" it can happen several times during the project development that the document is subject of change. In such a case the old IUS version is valid until a new IUS version is released. After releasing a new IUS version the preceeding IUS version enters the state "outdated".\r\n\r\nCurrently these specifications are written as Text Document (e.g. MS Word) which is not very convenient. Such documents are "too far away" from the SW developer. Additionally they cannot be easily referenced by tickets or changeset comments.\r\n\r\nThus_ I would like to ask for a mechanism in Trac supporting different states of Wiki pages.,enhancement,new,normal,Request-a-Hack,normal,,,fcorreia@gmail.com,0.10