Edgewall Software
Modify

Opened 15 years ago

Closed 14 years ago

#4716 closed task (fixed)

Prepare documentation for 0.11

Reported by: Christian Boos Owned by: Christian Boos
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)

Attachments (0)

Change History (19)

comment:1 by Christian Boos, 15 years ago

Milestone: none0.11
Severity: normalmajor

comment:2 by Christian Boos, 15 years ago

Priority: normalhigh

comment:3 by anonymous, 14 years ago

[[TracGuideToc]]

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

comment:4 by Christian Boos, 14 years ago

Milestone: 0.11.10.11

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

Please see

comment:6 by ThurnerRupert, 14 years ago

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

comment:7 by ThurnerRupert, 14 years ago

wiki:0.11/TracGuide that is …

comment:8 by Christian Boos, 14 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@…, 14 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@…, 14 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, 14 years ago

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

comment:12 by Christian Boos, 14 years ago

Description: modified (diff)

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

comment:13 by Christian Boos, 14 years ago

Well, at this point here's how I'm going to proceed:

  • review and merge the changes from the regular Wiki pages in trunk
  • review and merge the few additional changes from the 0.11/ Wiki pages

The 0.11/ Wiki pages were intended for contributors during the 0.11dev period, but somehow that didn't work out so well…

comment:14 by Christian Boos, 14 years ago

The content of the 0.11/ pages are now integrated in the corresponding toplevel pages, and the previous content of those toplevel pages has been saved in the corresponding 0.10/ page for the pages which have undergone big rewrites.

Of course, there's still a lot of editing that need to be done and this should now be done on those toplevel pages.

comment:15 by Christian Boos, 14 years ago

As of r6302, the TracGuide content is far from perfect, but that's a start which I think is OK for the beta1.

The TracDev/ReleaseNotes/0.11 is quite OK (if not a bit too detailed), and the TracDev/ApiChanges/0.10 is mostly done as well.

So let's go for the beta1 ;-)

comment:16 by ilias@…, 14 years ago

Cc: ilias@… added

comment:17 by Christian Boos, 14 years ago

Eli, can you please write a few words there: TracDev/ApiChanges/0.11

I think I'll soon do need another round of sync from the Wiki, if anyone feels there's something to add to the wiki documentation, it's the right time.

comment:18 by Christian Boos, 14 years ago

Owner: changed from Jonas Borgström to Christian Boos

Documentation is mostly in sync now and I think the changes and the new features from 0.11 are now mostly covered.

comment:19 by Christian Boos, 14 years ago

Resolution: fixed
Status: newclosed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Christian Boos.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Christian Boos to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.