Differences From:
File www/bugtheory.wiki part of check-in [6ecc392f1c] - Updated documentation to indicate that bug-tracking is now available. Preliminary documentation on bug-tracking. (Much more documentation is needed - also need documentation on how the wiki works.) by drh on 2008-07-20 17:37:10. [view]
To:
File www/bugtheory.wiki part of check-in [9d10726d48] - Documentation updates. by drh on 2008-07-29 13:07:17. [view]
@@ -31,14 +31,14 @@ One or more ticket change artifacts are associated with each ticket. A ticket is created by a ticket change artifact. Each subsequent modification of the ticket is a separate artifact. -The "push", "pull", and "sync" algorithms shared ticket change artifacts +The "push", "pull", and "sync" algorithms share ticket change artifacts between repositories in the same way as every other artifact. In fact, the sync algorithm has no knowledge of the meaning of the artifacts it is syncing. As far as the sync algorithm is concerned, all artifacts are -alike. After the sync has occurs, the individual repositories must try -to make sense of the meaning of the various artifacts for themselves. +alike. After the sync has occurs, the individual repositories must +make sense of the meaning of the various artifacts for themselves. <h2>Interpretation Of Ticket Change Artifacts</h2> Every ticket change artifact contains (among other things) @@ -54,14 +54,14 @@ or appended, according to a flag on the name/value pair. The current values for the fields of a ticket are the values that remain at the end of the replay process. -To create a new ticket, on has merely to insert a ticket change -artifact with a randomly generated ticket UUID. The ticket UUID -is a random 40-character lower-case hexadecimal number. New -ticket UUIDs should be chosen using good randomness so that two -ore more users do not accidently cause a conflict by generating -the same UUID. The name/value pairs on the initial ticket change +To create a new ticket, one inserts a ticket change +artifact with a new UUID. The ticket UUID +is a random 40-character lower-case hexadecimal number. The "tktnew" +page in the fossil web interface creates new ticket UUIDs +using a good source of randomness to insure uniqueness. +The name/value pairs on the initial ticket change artifact are the initial values for the fields in the ticket. Amending a ticket means simply creating a new artifact with the same ticket UUID and with name/value pairs for those fields which @@ -99,14 +99,23 @@ one row in the TICKET table for each unique ticket UUID. The names of columns in the TICKET table correspond to the names in the name/value pairs of ticket change artifacts. When running the replay algorithm, if a name/value pair is seen which has no corresponding column -in the TICKET table, then that name/value pair is ignored. +in the TICKET table, then that name/value pair is ignored. Columns can +be added or removed from the TICKET table at any time. Whenever the +TICKET table is modified, the replay algorithm automatically reruns +to repopulate the table using the new column names. Note that the TICKET +table schema and content is part of the local state of a respository +and is not shared with other repositories during a sync, push, or pull. Each repository also defines scripts used to generate web pages for creating new tickets, viewing existing tickets, and modifying an existing ticket. These scripts consist of HTML with an embedded -scripts written an a TCL-like language called "TH1". Each fossil -repository is create with default scripts. There is currently no +scripts written an a TCL-like language called "TH1". Every new fossil +repository is created with default scripts. There is currently no documentation on the TH1 langauage. Administrators wishing to customize their ticket entry, viewing, and editing screens should -modify the default scripts to suit their needs. +modify the default scripts to suit their needs. These screen generator +scripts are part of the local state of a repository and are not shared +with other repositories during a sync, push, or pull. + +<i>To be continued...</i>