river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [PROPOSAL] Source drop and bug database
Date Thu, 04 Jan 2007 19:01:45 GMT

On Jan 4, 2007, at 1:23 PM, Mark Brouwer wrote:

> Jim Hurley wrote:
>> Way back when :-)   under the SCSL, something similar
>> was named the "Technology Compatibility Kit" (TCK) and
>> was a legal measure for helping to ensure compliance for
>> commercial implementations.
>> I think some people have found it generally handy over
>> time to use to test their Jini service, etc -- so it might be
>> good to include.
>> Thoughts?
> I don't use it anymore, I rely on the utilities to do their work or  
> on a
> container, but I see value in having it. But I think it is better to
> introduce it after the project has started, just to prevent from  
> overload.
> This also raises a question, how are we going to manage all this. From
> SVN I get the impression the website is a separate branch in the
> repository, but do we have to check-in all 'subprojects' into one  
> trunk.

There's no such thing as a "branch" in SVN in the classic version  
control sense - branches are just copies into a new directory.

> In the end I hope the River project becomes a TLP with various
> subprojects such as core, lus implementation, javaspaces  
> implementation,
> etc.. Each with their own release schedule. Dumping everything in one
> trunk doesn't seem very handy to me, but as I already mentioned I'm an
> SVN infant so maybe this works out well. Anyone?
> -- 
> Mark

View raw message