Feature and change tracking information

New feature and change log commands

New features can be tracked version-based via using

*  @new{<mainversionnumber>, <mainversionnumber>, <developerkey>[, <date>]} <description>
*

For example, writing

*  @new{0,1,dw} Added a fancy new feature! (New feature Example)
*

results in

New in 0.1:: (Daniel Wirtz, undated) Added a fancy new feature! (New feature Example)

To include a date write

*  @new{0,1,dw,2011-01-01} Added a fancy new feature on new year's! (New feature Example)
*

results in

New in 0.1:: (Daniel Wirtz, 2011-01-01) Added a fancy new feature on new year's! (New feature Example)

and a new related page called newfeat01 listing these items. To refer to that Changelog page, use the keyword 'newfeat' together with both plainly concatenated numbers:

*  @ref newfeat01
*

gives newfeat01

Changes can be tracked version-based via using

*  @change{<mainversionnumber>, <mainversionnumber>, <developerkey>[, <date>]} <change-text>
*

For example, writing

*  @change{0,1,dw} Changed foo to bar! (Changelog Example)
*

results in

Change in 0.1:: (Daniel Wirtz, undated) Changed foo to bar! (Changelog Example)

The optional date works same as with the '@new' command. The related page keys for changes are composed by the keyword 'changelog' and both plainly concatenated numbers (similar to the new feature keys).