Edgewall Software

Opened 17 years ago

Last modified 16 years ago

#4716 closed task

Prepare documentation for 0.11 — at Version 12

Reported by: Christian Boos Owned by: Jonas Borgström
Priority: high Milestone: 0.11
Component: general Version: 0.10
Severity: major Keywords: documentation
Cc: ilias@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christian Boos)

Change History (12)

comment:1 by Christian Boos, 17 years ago

Milestone: none0.11
Severity: normalmajor

comment:2 by Christian Boos, 17 years ago

Priority: normalhigh

comment:3 by anonymous, 17 years ago

[[TracGuideToc]]

is not correct in e.g. in wiki:0.10/TracIni

comment:4 by Christian Boos, 17 years ago

Milestone: 0.11.10.11

comment:5 by martin.marcher@…, 17 years ago

Please see

comment:6 by ThurnerRupert, 17 years ago

added further documents to wiki:0.11, see also wiki/0.11/TracGuide.

comment:7 by ThurnerRupert, 17 years ago

wiki:0.11/TracGuide that is …

comment:8 by Christian Boos, 17 years ago

#6186 marked as duplicate.

There were a few discussions about this topic on either trac-dev or on trac-users. If I recall correctly:

  • the 0.9/*, 0.10/* and 0.11/* pages should contain version specific documentations
  • the toplevel pages should contain the main contributed docs, which usually cover the range of currently in use versions

Therefore, before the 0.11 release, we should "branch" the Wiki into the 0.11/ pages, eventually merge it with the documentation already in place and finally "prune" the non-relevant content.

Then, we push all these pages into the trac/wiki/default-pages.

in reply to:  8 comment:9 by ilias@…, 17 years ago

Replying to cboos:

#6186 marked as duplicate.

There were a few discussions about this topic on either trac-dev or on trac-users. If I recall correctly:

  • the 0.9/*, 0.10/* and 0.11/* pages should contain version specific documentations

ok, this would mean, that e.g.

wiki:0.11/TracInterfaceCustomization

should not contain documentation subjecting 0.9 ?

  • the toplevel pages should contain the main contributed docs, which usually cover the range of currently in use versions

e.g. wiki:0.11 contains the list of pages specific to 0.11

Therefore, before the 0.11 release, we should "branch" the Wiki into the 0.11/ pages, eventually merge it with the documentation already in place and finally "prune" the non-relevant content.

Then, we push all these pages into the trac/wiki/default-pages.

if I understand right, the pages listed in wiki:0.11 (e.g. wiki:0.11/TracInterfaceCustomization) will go finally into the repository 0.11 (wiki default pages)

all this sounds ok.

but doesn't this mean, that the following part from wiki:0.11/TracInterfaceCustomization should be removed?

 Note: in projects created with a Trac version prior to 0.9 you will need
 to create this folder.

comment:10 by ilias@…, 17 years ago

I've found this thread here, but cannot understand.

Possibly one should write the process down in the wiki, thus I know how to proceed to cleanup the 0.11 documentation.

  • do I file tickets, and the team changes in the repo?
  • or do I edit the onlie 0.11/ docu?

see additionally #6181 for a concrete example.

comment:11 by Christian Boos, 17 years ago

Critical part of the documentation to update ASAP: wiki:TracDev/ApiChanges/0.11

comment:12 by Christian Boos, 16 years ago

Description: modified (diff)

Changed prefix from Trac0.x/ to 0.x/

Note: See TracTickets for help on using tickets.