Fossil

Check-in [335d5295]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix typo in the event.wiki page.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 335d5295978a0714bcaff78f89d8c71103d2186dfff03a17f5924e03fac84f5c
User & Date: drh 2018-09-28 14:59:29.836
Context
2018-09-28
20:54
Document reference links having no second set of square brackets ... (check-in: 2856830e user: andygoth tags: trunk)
14:59
Fix typo in the event.wiki page. ... (check-in: 335d5295 user: drh tags: trunk)
2018-09-27
02:17
Guess that agents with "iPad" in their name do not want the narrow screen versions of the page. ... (check-in: b76eebea user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/event.wiki.
︙︙
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

  *  <b>Milestones</b>.  Project milestones, such as releases or beta-test
      cycles, can be recorded as technotes.  The timeline entry for the technote
      can be something simple like "Version 1.2.3" perhaps with a bright
      color background to draw attention to the entry and the wiki content
      can contain release notes, for example.

  *  <b>Blog Entries</b>.  Blog entries from developers describing the current
     state of a project, or rational for various design decisions, or
     roadmaps for future development, can be entered as technotes.

  *  <b>Process Checkpoints</b>.  For projects that have a formal process,
     technotes can be used to record the completion or the initiation of
     various process steps.  For example, a technote can be used to record
     the successful completion of a long-running test, perhaps with
     performance results and details of where the test was run and who








|








21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

  *  <b>Milestones</b>.  Project milestones, such as releases or beta-test
      cycles, can be recorded as technotes.  The timeline entry for the technote
      can be something simple like "Version 1.2.3" perhaps with a bright
      color background to draw attention to the entry and the wiki content
      can contain release notes, for example.

  *  <b>Blog Entries</b>.  Blog entries from developers describing the current
     state of a project, or rationale for various design decisions, or
     roadmaps for future development, can be entered as technotes.

  *  <b>Process Checkpoints</b>.  For projects that have a formal process,
     technotes can be used to record the completion or the initiation of
     various process steps.  For example, a technote can be used to record
     the successful completion of a long-running test, perhaps with
     performance results and details of where the test was run and who
︙︙