forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Tessner <r...@apache.org>
Subject Re: Plugin release process (was Re: svn commit: r109379 - /forrest/trunk/docs-author/status.xml)
Date Wed, 01 Dec 2004 23:09:42 GMT
Ross Gardler wrote:
> If this is ready for use please do an "ant deploy" in the plugin 
> directory, this will make the plugin zip available via the forest website.

Will do.  I've been trying the "ant test" and I get this very odd 
message during "validate-xdocs":

    -- begin message --
validate-xdocs:

BUILD FAILED
/home/rick/projects/forrest/van/plugins/build.xml:133: The following 
error occurred while executing this line:
/home/rick/projects/forrest/van/main/targets/validate.xml:143: Parser 
org.apache.crimson.parser.XMLReaderImpl doesn't recognize feature 
http://apache.org/xml/features/validation/dynamic

   -- end message --

My CLASSPATH is not set, FORREST_HOME points to the right place (in my 
case, /home/rick/projects/forrest/van) and "forrest site" and "forrest 
local-deploy" work just fine ... I'm at a bit of a loss ATM. :(

> At present there is no release process for plugins. We have simply been 
> releasing them when new features have been added.

Okay.  I guess this plugin should follow the naming convention as well. 
  I'd like to do that before I deploy it.  If I understand the 
convention correctly, it should be:

   org.apache.forrest.plugin.text-output

> However, we will need to manage the official release of plugins (which 
> should also include a publishing of the plugin documentation to the 
> website).
> 
> How should we manage this process?

At this point, I'm not sure what the manual process would be either. 
Plugins would certainly have a different release cycle than Forrest itself.

I'll just start putting together a list that is by no means 
comprehensive and hopefully others will add/correct this list:

1.  Identify the Forrest releases that the plugin is compatible with.
2.  Deploy the plugin to the release site somehow identifying Forrest 
version compatability.
3.  Updating the plugin documentation for each release it is compatible 
with.
4.  Announcing availability of updated / new plugin.

> PS Thanks for your great work on this Rick, I will shortly need to 
> update the site I wrote the original xdoc2txt stuff for. It is superb 
> that I won't have to refine the code before the next update. (I love 
> Open Source)

Thanks and yup, this Open Source stuff is awesome!

-- 
Rick Tessner
rick at apache dot org

Mime
View raw message