> Have you been able to finish the new release yet?
Just released 0.9.4 last night. I took a little longer because I just HAD
to automate my release process as it was taking more than a day just to
complete all the parts (run tests, tag CVS, make packages, upload to
sourceforge, go through the overly complex SF release process without
error, run apidocs, upload apidocs, upload changelog, announce to
mailinglist, and announce to freshmeat). It isn't all automated yet, but
major steps have been taken (I am using Apache Ant if you didn't notice
already). Word of advice for anyone who is running a project, automate
everything, including the coffee maker, or else your life will become
insane very quickly.
> Please let me know if I can help with something!
The biggest help you could provide right now (at minimal cost to you) is to
add some of the feature requests/bugs to the sourceforge tracker. I know
what needs to be done with Studs, but others don't yet. This will be a
good chance for you to get what you want and for me to pave my path.
I have also found some criticism to studs on the 'net. We need to get
these discussions going on the mailinglists so that we can be sure to
write the best code possible. Issues I know will come up are automatic
reload of struts-config.xml on change, departing from Struts where it
falls short, etc. Again, I have ideas, but if this is going to be a
community project, we just need to start throwing out that info.
In summary, add stuff to tracker, throw out ideas on mailinglist. I am
extremely tough, so try me. I would rather people bash on the project
than to remain in solitude.