Talk:Plugin shop

--DenisChenu (talk) 15:51, 16 March 2018 (CET) About plugin update : need to have a compatibility system , then , before i think we must have a compatibility system for plugin itself (inside LS).

• compatible => [3.5,3.*] : compatible since 3.5.1, and current 3.X release surely next (but can not be sure)
• compatible => [3.0,3.99]  : compatible for 3.0 branh
• compatible => [3.0,4.99]  : compatible for 3 and 4 branch
• compatible => [3.0,4.*]  : compatible for 3 and current 4 version

And maybe more :

• tested => [3.5.2,3.6.1] (with a [3.5,3.*])

Another idea is 'state'=> '(stable|test|dev)'

And the 'update url'

Can't we assume that if the plugin is compatible with 3.5, the it will also be compatible with 3.6, 3.7, etc, for all coming 3.x versions? Olle (talk) 16:11, 16 March 2018 (CET)

We can assume, but you know it can be false … A lot of plugin use model function or limesurvey global function etc … I just see a plugin call another view (not mine), and this view was updated between 2.6 and 2.7. --DenisChenu (talk) 16:53, 16 March 2018 (CET)

We can include 'state', but it's not relevant for LimeSurvey GmbH and the plugin shop, because if it's on the shop it should always be stable. Olle (talk) 16:18, 16 March 2018 (CET)

You mean shop like 'Pay to have plugin' ? --DenisChenu (talk) 16:53, 16 March 2018 (CET)

Else : maybe included limeservice “shop” include only stable, but have a config.php setting to allow test ?

And repo url updatable only via config url (then i can add my 'testing and debug' repo url on a mssql dev instance for example And Tammo or other team can easily test new beta plugin --DenisChenu (talk) 16:56, 16 March 2018 (CET)