Hi everyone, Thanks to Emmanuel for posting. I would just like to clarify that the 5.0 Feature "Support for certification-based transactional replication protocols" includes supporting the GORDA contributions in the gorda.db.sequoia.* packages currently stored in CVS HEAD. GORDA has interesting interceptor model designed to support multiple replication mechanisms that looks like a good candidate to replace the interceptor model I began to add to Sequoia last year.
We will also be following up with some specifics about codeline setup for Sequoia 4.0 as well as build support. In addition to providing the stable code from 2.10 that we have been beavering away upon for the last year or as a basis of 4.0, there are two things that we plan to provide going forward: - The MATs (Minimum Acceptance Tests) mentioned by Emmanuel. - Regular build and test runs of Sequoia from our build facility in New York. This will likely include setting up CruiseControl builds, which are completely cool. Miscreants who break stuff (as Manu and I have both done on more than one occasion) will be found out and publicly humiliated. I can't wait. Please weigh in on your desires. As we finalize the roadmap we will abolish the JIRA release entry for Sequoia 3.0 and create new JIRA entries for Sequoia 4.0 and Sequoia 5.0. This will occur over the next week or so. So please sound off on the list. We want to hear from you. Cheers, Robert On 3/27/08 12:25 PM, "Emmanuel Cecchet" <[EMAIL PROTECTED]> wrote: Hi all, It is time to plan for new Sequoia developments. Here is a roadmap proposal for Sequoia 4.x and 5.x. As 3.0 is now obsolete, the goal is to start a new 4.0 version based on the current 2.10.10 code base. We need to define the feature set that will go in Sequoia 4.x and 5.x so that the open source version (in HEAD) can move forward as fast as the feedback comes from the community, but it remains stable enough so that Continuent can elaborate products on stable versions. Your feedback is very important if you want to get your requirements included. This is the time to influence the design and evolution of Sequoia. Sequoia 4.x features: - Controller configuration cleanup (based on 3.x implementation): Mandatory JMX, fix JDBC/JMX IP/port configuration, SSL configuration refactoring, remove deprecated AccessControl and Internationalization. - New virtual database autoload feature including loading files through HTTP - Support for semantic information (as in 3.x) to support pluggable parsing, stored procedures, ,views and triggers - Cleanup obsolete load balancers/schedulers (RAIDb1-ec, RAIDb2-ec...) - Cluster-wide shutdown to allow controller restart in any order - Pluggable DatabaseBackend implementations for database specific preconfigured implementations (ie. MySQLBackend, OracleBackend... simplifies vdb config) - Pluggable RecoveryLog implementations for database specific preconfigured implementations (simplifies vdb config) - Tunable macro handling (as currently available in 3.x) - Support for host-based access control in virtual database (as in 3.x) - Support for default cluster-wide admin user - Drop support for static schemas - Mandatory Backup element - Mandatory Recovery Log element (Does anyone use a controller without recovery log?) - Support for default connection manager and different URL options in connection pools (as in 3.x) - Drop JDK 1.4 support (move to JDK >=1.5 and clean code accordingly) - XML parsing refactoring - Support for embedded controllers - Open source test suite contributed by Continuent in GPL (will start in May with Minimum Acceptance Tests) Sequoia 5.x features: - Controller metadata repository to persist controller state with automatic shutdown/restart procedures - Support for certification-based transactional replication protocols - Support for transactional upgrades and management operations - ResultCache refactoring and optimizations - JDK >=1.6 only with JDBC 4 support - Extend test suite with pluggable virtual appliances containing contributed 3rd party database - Resume Oak project (Eclipse RCP graphical console) Not scheduled yet: - Split code in multiple projects: load balancer (single controller configuration), high availability (multiple controllers) - Virtual RDBMS (manages a RDBMS globally, not on a per virtual database instance) - Unique cluster-wide configuration file Your feedback is welcome and we are going to publish soon the roadmap on the Sequoia web site. I should start working on Sequoia 4 next week so don't hesitate to step up! Best regards, Emmanuel -- 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
