Re: [ jEdit-devel ] My "last" plugin batch

[Calvin Yu <cy...@ya...>]

These are good questions.  We need to take this oppourtunity to discuss 
possible ways of automating most of these tasks.  There was some talk 
before about standardizing the directory structure of all plugins and 
creating a generic build file which can build any plugin, I think we should 
expand on that so that we don't overwhelm our next build/release manager(s) 
.  In fact, I think our end goal should be to make the need for such a 
person to be non-existant.  Here are my thoughts on this:

* Create a way for plugin maintainers to notify a build system of plugins 
ready for release.

* One generic build file which can build all plugins (I'm sure there will 
be some exceptional plugins, we'll worry about those later).

* A 'compatibility kit' which will run after a build to ensure that the 
plugin meets requirements for release to PC. (What are those requirements?)

* Automatically upload plugin to PC after the build, compatibility check, 
and maybe confirmation from a release manager.  Automatically send an email 
to mailing list.


Calvin


On 09 May 2003 11:19:59 +0200, Stefan Kost <s....@we...> wrote:

> Hi Mike,
>
> can you think of some workflow, which would allow plugin-teams to do the
> releases themselves? Points I belive it would involve
> * ant dist
> * verifying that it works
> * upload to plugin central
> * mail a message to jedit-announce
> Please comment on it. And thatnks alot for you past work. You did a
> great job.
>
> Ciao
> Stefan



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/