But Drools isn't being developed according
to some standard Development Life Cycle.
Not true, but the development process should be documented more. See
/README.txt
Well... Basically, we agree ;-)
We have plenty of things already set-up. Most recently we defined
they idea focusing on "branch day" instead of "release day".
Feel free to open discussions on any other improvements we should
do: you're right there's much to do. But 1 at a time please, so
people can adjust to them.
A recent exchange with Edson/IRC has brought up a "howto" for the full branch - change - push cycle. I'm collecting...
Next thing is the split-up of the build and repositories (if
possible).
Ah, a consummation. Devoutly to be wish'd!
After that we'll look into a lieutenant git model per repository,
which is basically the coordination CM role you speak of :)
Great.
-W