Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <521788660.1118872006805.JavaMail.jira@ajax.apache.org>
Date: Wed, 15 Jun 2005 23:46:46 +0200 (CEST)
From: "Juan Jose Pablos (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Updated: (FOR-528) Add version control to plugins
In-Reply-To: <72307691.1118217558649.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/FOR-528?page=all ]

Juan Jose Pablos updated FOR-528:
---------------------------------

    Component: Plugins (general issues)

> Add version control to plugins
> ------------------------------
>
>          Key: FOR-528
>          URL: http://issues.apache.org/jira/browse/FOR-528
>      Project: Forrest
>         Type: Test
>   Components: Plugins (general issues)
>     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 pluginname-0.7.zip and a pluginname-0.8-dev.zip
> 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 example)
> How about I change it to put the plugins in a directory so we have:
> 0.7/plugingOne-0.1.zip
> 0.7/plugingTwo-0.2.zip
> 0.8-dev/pluginOne-0.2-dev.zip
> 0.8-dev/plugingTwo-0.2.zip
> 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 http://marc.theaimsgroup.com/?l=forrest-dev&m=111821546807300&w=2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira