Re: OSW: doAction, codebase, features and Roadmap

> I agree with a lot of your points, to be honest. AbstractWorkflow is a
> very ugly class with some pretty nasty code (sorry Pat!)
> We definitely will be looking at refactoring it and making it much more
> straightforward to extend and enhance for the 3.0 release.

The only one that should be sorry is me ;) Yes, 3.0 will make the code MUCH
nicer we hope.

<snip>

Help would always be very much appreciated. I agree with Hani about CVS
access (too many possibly hurt), but the more help usually the better. I
think that all of OpenSymphony needs to make releases more often. It turns
out that making releases is one of the more painful things (just behind
documentation), so help in either of those areas would be most appreciated.

-Pat




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge