On Mon, 15 Jan 2001, Magnus ?or Torfason wrote:
> Not that my vote counts, but I am getting pretty restless
> waiting for a release. I have to make MY releases, and
> any bugfix that is applied to Turbine means that I have
> to upgrade Turbine, and then go through my code and update
> that, since there is some modified functionality in Turbine
> or Velocity.
I think the only things absolutely required right now for
a release are a revamp of the docs and a testbed. I think
these two things are an absolute must. After that I think we
could release, I just think some code cleanup and reworking
of services would be good.
If you are getting restless then help with the docs and
help make a testbed!
> What about making a 0.5 release (or we can refuse to call it
> a release) but just to make a branch in CVS that no development
> takes place on (only bugfixes). There are a lot of people that
> are depending on Turbine (me for one), and there is a growing
> risk of frustration.
This is why I'm trying to take in informal poll as to how
many people a service change would actually affect. My
intention is not to pull the rug out from anyone.
> As for a new service model specifically, this would pretty
> certainly break my property file layout for one. And does
> it imply that I have to write my own services all over again?
It would probably require some properties file changes, but
it certainly wouldn't entail a rewrite. I think any functionality
required for pluggable services could be place in a base class
so that at most you would require some import statement changes
and a recompile.
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
