Hi Stephen,

> * Nikolay Molchanov <[EMAIL PROTECTED]> [2006-02-16 20:30]:
> 
>>I know that "OpenTeamware" project has achieved its milestone 1 (please, see 
>>the 
>>announcement below; it was sent to [EMAIL PROTECTED] alias).
>>The binaries and sources are available for internal use. Standard TeamWare 
>>tests
>>show that the quality of the binaries is good (there are several failed 
>>tests, but they
>>are not critical), so these binaries can be used as a candidate for contest.
>>This version is expected to show very good performance in "update" 
>>transactions,
>>especially in case the workspace is large, and the changes are small (less 
>>than 10%).
> 
> 
>   The appropriate next step would be to submit an assessment against the
>   existing requirements document.  For myself, I am curious about E2
>   (transports other than NFS), E4 (directory operations in particular),
>   C8 (community development plan), C10 (non-mail-based hooks), and C11
>   (identification of partially successful operations), with respect to
>   the binaries made available in this release.

I posted an assessment against the existing requirements document:

http://www.opensolaris.org/jive/thread.jspa?threadID=6528&tstart=0

Unfortunately could not post it earlier, so even if it is too late,
better late than never. Please, let me know if the sections E4, C8,
C10, and C11 are not described good enough. There is still an open
issue with section E2 (transports other than NFS). I have a solution,
but it will take some time to add this feature to the OpenTeamware
sources, and I'm still in conversation with OpenTeamware development
team about this change in their development plan, so no date yet.

Thanks,
Nik
__________________ Nikolay Molchanov
SUNSTUDIO/DMAKE/MAKE/SCCS, Sun Microsystems
email: [EMAIL PROTECTED]
phone: (650) 786-7643 (x87643)
------------------------------------------------------------
NOTICE: This email message is for the sole use of the
intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited.
If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the
original message.

_______________________________________________
tools-discuss mailing list
[email protected]

Reply via email to