
How to enter documentation for new Versions of MediaPortal.
As a result of our new Documentation Policy, all changes made to MediaPortal which affect Skins, Plugins, Language files or the user interface (GUI) must be documented prior to a release of MediaPortal.
Our Mantis Bug Tracker now includes a Docs Req'd field for each issue. Any issue which changes the User Interface (UI) installer, configuration settings, language (strings) files, or affects Skins or Plugins development is marked for documentation (Docs Req'd = Yes).
As soon as the Mantis Issue is 'resolved', documentation should be added to the appropriate section of the wiki. When the documentation is complete, the Docs Req'd field is set to Done, and a note is added with the link(s) to the related Wiki page(s).
There are several benefits to this policy:
| Change related to | Wiki Section | Template | How To Use |
|---|---|---|---|
| Skins | Skin Related Changes | Skin or Plugin Related Changes | How to Add Skin Changes |
| Plugins | Plugin Related Changes | Skin or Plugin Related Changes | |
| Strings | Strings Changes | none - enter changes on the page | |
| UI (GUI, Config, Installer) | What's New | UI Related Changes | How to add UI Changes |
The templates include instructions to ensure changes are documented consistently and completely.
As of v1.3.0+ the process for documenting changes to the UI (GUI, Config tools, Installer (Deploy tool) has changed: