forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: release process for our plugins
Date Sat, 03 Jul 2010 09:17:53 GMT
David Crossley wrote:
> David Crossley wrote:
> > I have been doing some more review, and will attempt to
> > present a proposal soon.
> 
> Still :-)
> 
> > --------------
> > The following do not have an entry in the plugins
> > descriptor file whiteboard-plugins.xml and have never
> > been deployed to the website ...
> > Database, OpenOffice.org-output, Blog, Lenya,
> > DevTools, GoogleSitemap, rtf-output
> > 
> > --------------
> > The following do have an entry in the plugins
> > descriptor file whiteboard-plugins.xml
> > However they have never been deployed to the website
> > which probably creates confusion ...
> > Resume, XDoc, baetle, doac, ecs, foaf, skos, input.tei,
> > NoteTaking, xhtml2, output.OOo, iCal, output.tei
> > 
> > Some of those might not be relevant to deploy yet,
> > but some are probably okay.
> 
> I found a useful-looking attribute while browsing
> the plugin build.xml files.
>   <!-- The plugin will only appear in the plugins list if publish = true
>   <property name="publish" value="true"/> -->
> 
> If they are not ready enough to even have an
> initial deployment then we can list them differently.
> So people can still know about them and get interested.

I have finished the work with presenting plugins
in the plugin lists.
See http://forrest.apache.org/pluginDocs/

Also done a review and synchronisation of the configuration
aspects of all plugins.
See $FORREST_HOME/etc/review-plugin-deployment.txt

Still working on a proposal for getting many plugins
out of the whiteboard and properly deployed.

Don't let that hold anyone up from working on the
Forrest release. With our current release process,
plugins have a separate release cycle to the core.

-David

Mime
View raw message