Plugin Versioning

[AJ Mercer]

I have been thinking for awhile, and stimulated by Geoff's interview on cfConversations, about plugin versions.

Geoff was saying that if developers what to utilise the full power of the latest release of the CFML engine, a plugin can be created that can override the functionality of the Farcry core or Farcry CMS; as Jeff C has down with his image plugin to take advantage of the CF8 image tags.

But what I was wondering if plugins should have a version; so for example, V1 of Jeff's image plug in works with CF8, and V2 works with CF9

And then I guess if there are comtomisation for specific CF Engines, eg Railo or OpenBD, then they should be categorised some how too.
So if there was a video plugin that utilised Railo's CFvideo tags, you would know not to bother installing it on CF8.

And finally, what version of Farcry Core and Farcry CMS plagin are compatible?

--
AJ Mercer
Web Log: http://webonix.net



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---

[Blair McKenzie-2]

Our plugins are versioned the same way as core.

The major version is incremented if there are backwards compatibility issues, and for major version changes in core. The plugin is usually branched at the same time.
The minor version is incremented if there are "mindset" adjustments needed - new features, removed functionality, or if something behaves differently.
The patch version is for bug fix releases.

So, if you look at the FarcryCMS plugin repo you will see that there is a branch (p100) for FarCry 4.x support, trunk which corresponds to the latest version 2.x for 5.x (and typically the only version that will get new features added), plus various 1.x.x and 2.x.x tags for actual releases. If FarcryCMS was updated to rely on 5.1 features we would create a maintenance branch for 2.x (p200), and trunk would be 3.x.

I'll try to update the FarcryCMS plugin page to reflect the current relationships soon.

Blair

On Wed, Nov 12, 2008 at 11:22 AM, AJ Mercer <ajmercer@...> wrote:

I have been thinking for awhile, and stimulated by Geoff's interview on cfConversations, about plugin versions.

Geoff was saying that if developers what to utilise the full power of the latest release of the CFML engine, a plugin can be created that can override the functionality of the Farcry core or Farcry CMS; as Jeff C has down with his image plugin to take advantage of the CF8 image tags.

But what I was wondering if plugins should have a version; so for example, V1 of Jeff's image plug in works with CF8, and V2 works with CF9

And then I guess if there are comtomisation for specific CF Engines, eg Railo or OpenBD, then they should be categorised some how too.
So if there was a video plugin that utilised Railo's CFvideo tags, you would know not to bother installing it on CF8.

And finally, what version of Farcry Core and Farcry CMS plagin are compatible?

--
AJ Mercer
Web Log: http://webonix.net

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "farcry-beta" group.
To post to this group, send email to farcry-beta@...
To unsubscribe from this group, send email to farcry-beta+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/farcry-beta?hl=en
-~----------~----~----~----~------~----~------~--~---