Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Thu, 12 Apr 2007 13:41:31 +1000
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: [Poll] your interest in plugins to be deployed
Message-ID: <20070412034131.GI8244@igg.indexgeo.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i

It would be good to deploy any plugins that are
favourites for current developers.

Would developers please indicate which plugins
they want from the list at:
http://forrest.apache.org/pluginDocs/dev/index.html

One of the committers will press its deploy button.

This would mean that you have the most recent state
of a plugin available for use. Otherwise, and this
might be better for some, developers would need to
use an svn checkout.

The issue is that some plugins have been worked on
and further developed, but are not recently deployed.

   -----oOo-----

Doing "deploy" means to copy the pluginName.zip to
the website at f.a.o/plugins/0.8/ etc.

Doing "release" would be a different thing.
It appends a specific number, e.g. pluginName-2.zip
So it can be directly referenced. We will attend
to that after the 0.8 release of the core.

-David