pippin;352047 Wrote: > Why can't you go to a version scheme where beta versions actually have a > subversion of the preceding release, like 7.2.99? > That would allow beta testers to run plugins and issues would be known > by the time of the release. You can require beta testers to care for > plugin compatibility themselves, they have to anyway, since plugin > developers have no chance to always keep up with the changes during a > beta phase. > > Would probably give you better validated plugins by the time the > release comes out.
I like the current version numbering, as it gives my code an easy way to determine what version of SC is running, and therefore which APIs to use. I think it''d be better to add a maxSupportedVersion to install.xml so you could specify minVersion 7.+, maxVersion *, maxSupportedVersion 7.2+. If SC started to load a plugin where maxVersion was OK but maxSupportedVersion was not, it could offer a checkbox and warning in the web plugins page to force loading that plugin on the next restart of SC. Casual users probably wouldn't see & use the checkbox, reducing support headaches. -- peterw http://www.tux.org/~peterw/ free plugins: http://www.tux.org/~peterw/#slim AllQuiet BlankSaver ContextMenu FuzzyTime KitchenTimer PlayLog PowerCenter/BottleRocket SaverSwitcher SettingsManager SleepFade StatusFirst SyncOptions VolumeLock ------------------------------------------------------------------------ peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107 View this thread: http://forums.slimdevices.com/showthread.php?t=54051 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
