forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <>
Subject [jira] Updated: (FOR-528) Add version control to plugins
Date Fri, 10 Jun 2005 13:50:56 GMT
     [ ]

Ross Gardler updated FOR-528:

    type: Test  (was: Improvement)

> Add version control to plugins
> ------------------------------
>          Key: FOR-528
>          URL:
>      Project: Forrest
>         Type: Test
>     Versions: 0.7-dev
>     Reporter: Ross Gardler
>     Assignee: Ross Gardler
>     Priority: Blocker
>      Fix For: 0.7-dev

> David Crossley wrote:
> > Ross, are you able to explain what needs to happen with the plugins
> > at release-time. I mean do they all need to have "-0.7" appended
> > to the names of the zip files?
> Blast I forgot that entirely (again!). Yes we need two zipped versions, a
and a
> The system will then download the correct version for the currently installed version
of Forrest. This will allow us to have a separate release cycle for plugins, if we deploy
from a 0.8-dev version of Forrest then we will have the 0.8-dev zip file.
> However, now I write that down I don't like it because there is no distinction between
a 0.1 version of a plugin for Forrest 0.7 and a 1.0 version of a plugin for Forrest 1.0 (for
> How about I change it to put the plugins in a directory so we have:
> 0.7/
> 0.7/
> 0.8-dev/
> 0.8-dev/
> We only allow *-dev plugins in the current *-dev branch of Forrest
> We can worry about the release process for plugins after this release (just get them
out there for 0.7, we can blow the trumpet on subsequent upgrade releases)
> > Do we need to add something to our RELEASE_BOTES.txt file?
> Yes, a section on plugins with a link to the plugins page, I'll add to project-info plugin
> > Does someone need to tweak the build file?
> Yes, leave it with me, I'll implement the above with whatever modifications people think
we need.
> Ross 
> (for follow ups see

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message