Changes between Version 1 and Version 2 of PluginCompatibility


Ignore:
Timestamp:
Oct 3, 2017, 1:39:14 AM (4 years ago)
Author:
Ryan J Ollos
Comment:

Grammar fixes.

Legend:

Unmodified
Added
Removed
Modified
  • PluginCompatibility

    v1 v2  
    11111. Ask on the [trac:MailingList#Trac-users trac-users mailing list].
    1212
    13 If you find the plugin to be compatible with particular Trac version you can be a good citizen by updating the project page tags. See HackProcedures#Tagguidelines for details.
     13If you find the plugin to be compatible with a particular Trac version, you can be a good citizen by updating the project page tags. See HackProcedures#Tagguidelines for details.
    1414
    1515It can sometimes be difficult to determine which source you should install, even for a plugin that claims to be compatible with your Trac version. Plugins often use a directory structure where the basename is the Trac version that the plugin was developed for (e.g. `0.11` or `1.0`).  The code in that directory will often be compatible with later Trac versions, as much of the API does not change from release to release. In fact, there were few breaking API changes from 0.11 to 1.0, and many changes in Trac 1.2 when deprecated code was removed from the API. The code in a `0.11` directory is likely compatible with Trac 0.12.x, and may even be compatible with 1.0.x and 1.2.x.  See [trac:RoadMap#MilestoneCategories] for information about the Trac versioning convention.