Hi,
I just wanted to address a couple issues that have come
in the course of suggesting a change for the way
services works.
I agree that getting some form of stable release is
important so I propose the following plan.
We are going to be moving over to Jakarta soon, and
appears to require that we change the layout of
our repositories. Right now now we have two modules
in different directory structures: turbine and tdk.
Typically all subprojects in a Jakarta project are
kept in the same directory. Tomcat 4.1 consists of
jasper, catalina, and webapps. They are all different
components but are kept within the same directory
structure. So we could do the same and have turbine and
tdk. I would also like to add a third for now, flux,
which is the admin app.
So what about the following:
1) Reorganize the the turbine, tdk, and flux repositories
so that they reside under a single directory in preparation
to a move Jakarta.
2) Reorganize the util/service code simply to group common
code together, forget about the pluggable services
for now. This way even when we do add pluggable services
the packages should pretty much stay the same and not
cause much grief. But I definitely think the code
has to grouped better before release.
3) Clean up the docs.
4) Add a testbed
5) Release
Somewhere in this cycle I guess we will move to Jakarta,
or if we are ready to release will we just go to turbine.apache.org.
The pluggable services can wait, if we want to get a release
out then I say we feature freeze and over the next two weeks
try and get the docs and some form of a testbed going.
After we release then we can focus on changing the way
services work and general improvement, but for now
lets try and get a release out. Is there anything
really missing (besides docs, and testbed) that would
prevent us from releasing?
If we agree, I can 1) tonight, and start 2) tomorrow night
to get the ball rolling. I believe there are few people who
want to work on the docs, and there is a start of a testbed.
I think the testbed will probably be the biggest hurdle but
I think something is necessary, I don't you can release a
piece of software without a testbed.
Can we agree on this and get the ball rolling?
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
