Hi everyone,

We will need to put the test suite in a separate project as it will be under 
GPL v2 license.  We will be making some changes for new and some existing open 
source projects as far as licensing:

1.) Existing Apache licensed projects (Sequoia, Hedera).  No changes!

2.) Bristlecone.  No changes!  It's GPL V2 and we welcome contributions from 
the community.   The test suite will be licensed in the same way.  It will be 
based on our existing tests.

3.) Myosotis connector and new projects including distributed cluster 
management and a top-secret but very interesting project having to do with 
replication.  GPL V2 with contributions only from Continuent or on condition of 
transferring copyright.  (The MySQL model-we need to dual license some things 
to make house payments.)

As for start-up and shutdown.  We are going to release a cluster management 
framework that will take care of start-up and shutdown.  We would like to 
decouple the tests as much as possible from these operations, though it turns 
out some tests need to be able to kill both controllers and databases in order 
to test failover correctly.  The management framework has an API you can call 
from Java.

I'll post more on the cluster management framework in the very near future, as 
well as the tests.   Incidentally, we are also working internally on getting 
Sequoia under CruiseControl where it belongs.

Cheers, Robert

On 4/15/08 6:48 AM, "Stefan Lischke" <[EMAIL PROTECTED]> wrote:

Hi,

I give +1 for putting the test suite in the sequoia code base. Your
argument is good, it must be possible to check out any tagged version
and running the test cases corresponding to this state of development.

You started the test suite from scratch or are you using stuff provided
from continuent?
I thought about the suite some time and i don't have the perfect idea on
how to automate the cluster setup/shutdown for the tests.


Stefan

Emmanuel Cecchet wrote:
> I was wondering if we should include the test suite in the Sequoia
> code base or in a separate project.
> It could make sense to have the tests in the same repository to avoid
> maintaining branches in sync in both projects but all comments are
> welcome.




--
Robert Hodges, CTO, Continuent, Inc.
Email:  [EMAIL PROTECTED]
Mobile:  +1-510-501-3728  Skype:  hodgesrm
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to