Last modified by Vincent Massol on 2022/02/09 14:21

From version 4.1
edited by Vincent Massol
on 2020/02/21 09:38
Change comment: Update after https://forum.xwiki.org/t/improve-the-definition-of-a-recommended-extension/6317
To version 4.2
edited by Vincent Massol
on 2022/02/09 14:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,7 +10,7 @@
10 10  ** The extension has to continue to satisfy the following criteria to keep being recommended
11 11  *** There have been no bug issue updated within the past rolling 365 days. JQL = {{code language='none'}}project = “xxx” AND updated >= -365d and type = Bug{{/code}}
12 12  *** Or there have been bug issue updated within the past rolling 365 days BUT there have also been issue fixed during those past 365 days. JQL = {{code language='none'}}project = "xxx" AND updated >= -365d and resolution = Fixed{{/code}}. Note: that we consider here that even if the closed issues are not bug ones, it’s enough to justify that there’s been activity to the extension.
13 -* Works at least with the latest stable XWiki versions and with the LTS version
13 +* Works at least with the latest stable XWiki versions and with the LTS version (when possible. Sometimes an extension will require some new API only available in the stable version)
14 14  * Presents a polished aspect and is easy to use
15 15  * Mostly follows [[the best practices>>dev:Community.ApplicationDevelopmentBestPractices]]. Important aspects that must be followed:
16 16  ** Technical pages are hidden

Get Connected