Re: ThreadPool and NetServe Release?

Hi,

From: "Mauro Talevi" <[email protected]>
> Peter Donald wrote:
>
> > ThreadPool and NetServe are about due for a release? ThreadPool first as
it
> > NetServe depends upon it. ThreadPool has Pico and Phoenix/Loom
compatability
> > while NetServe is just Phoenix/Loom atm. I added some issues into jira
to
> > reflect what needs to be done. Anyone want to volunteer to go through
the
> > release process?
>
> NetServe PicoConnectionManager now also is Pico-compatible.

yea!

> There are no other Avalon-specific implementations in netserve so should
> be easy to make both components pico-compatible before release.

kool.

It may also be a good idea to add in DNA implementations if we have time. Or
else we can just do it next release.

> I can do the release - but we need to decide if we are going to go
> through a beta version or not for each component.

We could just do a simple RC/beta build and if no problems are found just
release it. Then again it may be easier to just release and re-release on
problems. I am easy either way.

> We need to complete clover coverage on both threadpool and netserve.
> I would say that is a prerequisite.

kool. ThreadPool should be easy to get coverage on. However Netserve is
going to be a real PITA to do. The only way that we can do it as far as I
can tell is to write MockSocket, MockServerSocket and corresponding
Mock*putStreams which is a lot of work. It may be worth it though as it will
allow us to guarentee quality better.

Maybe we do a final release of ThreadPool and a beta of NetServe and then
when we convert the unit tests we release a final NetServe?

> I've also finalised the clover unit test coverage for LoggerStore.
> That is ready for release too.

Kool! Added a JIRA issue for this.

Cheers,

Peter Donald



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf