forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: Managing plugin releases
Date Wed, 26 Jul 2006 13:46:42 GMT
Gav.... wrote:
>>-----Original Message-----
>>From: Tim Williams []
>>Sent: Wednesday, 26 July 2006 8:41 PM
>>Subject: Re: Managing plugin releases
>>On 7/26/06, Ross Gardler <> wrote:
>>>Tim Williams (JIRA) wrote:
>>>>Discussed here to:
>>>>I still agree with what I proposed in that mail.  
> Me too.
> I actually like
>>Ross' suggestion too but only if we move towards better
>>packaging/managing/releasing of plugins.
> Me too.
>>>What do you think is needed?
>>o) Independent/PMC managed releases
> Separating forrest collective written plugins from contributed plugins?

Separated how? To what end?

> Would there be a 'entire collection' packaged zip containing every released
> plugin?

Having a singe collection is not possible if each plugin has an 
independent release cycle.

>>o) Improved versioning - externally identifiable.  So that users might
>>be able to uninstall v0.3 of a plugin and reinstall 0.2 of a plugin.
>>I'm talking about manually not automagically.
> I agree, would the externally identifiable mean a naming convention to
> include the version number and compatible forrest version number?

The Forrest version information is already in the plugins.xml file. It 
could be placed into the plugin name too, but why does it need to be 
duplicated in this way?

Won't it get confusing? e.g. "pluginName-0.7-0.8" - which is the Forrest 

If not confusing then won't it be too verbose? e.g. 

I'm not saying it can't be done, I just don't see the need for the 
Forrest version in the filename. The plugin version is allready in the 
filename, the Forrest version is in the URL [1].



View raw message