From: Crawford C. <cc...@c-...> - 2006-01-18 09:32:03
|
Colas Nahaboo wrote: >On Tue, 17 Jan 2006 21:28:43 +0100 >André Ulrich <and...@st...> wrote: > > >>Ok, but isn´t this a general problem? >> >> > >Also, one could think that if they don't upgrade they will not upgrade their >plugins either (fear of breaking things), so the point is - IMO - moot... > > The point (I guess) is that Cairo users may want to leverage plugins fixes that are written since TWiki-4.0.0 in their Cairo releases, without being forced to upgrade their core. This is a call that needs to be left to the plugin author. If an author wants the widest possible audience for their plugin they will write compatibility code. If they need TWiki-4.0.0 functionality, then they won't (though presumably older versions of the plugin remain available). We never had this discussion at the release meeting; but FWIW here's my view: 1. /Links/ to Plugin versions compatible with Cairo should be gathered in a single topic e.g. Plugins.CairoPlugins. * i.e. links to viewfile of the appropriate rev in the plugin topic * Plugin authors may want to link to more recent versions here if they release updates compatible with both Cairo and TWiki-4.0.0 2. As part of the TWiki-4.0.0 release process, Plugins topics on twiki.org should be updated to the versions in subversion * this can be done by a script simply iterating over all the plugins, doing a perl build.pl upload for each 3. The front page of the plugins web should be updated to document this. C. |