As we are nearing the end of our Needle 2.0 development cycle, its time to start talking about release schedule. First some definitions: alpha: nearly feature complete, may be missing a few features and config format/ABI not completely stable, possible bugs. beta: feature complete, no missing features, stable ABI & config file format, possible bugs. release candidate: no new features allowed during development. man page updates acceptable (and encouraged to bring our man pages up to date). Changes to C code not allowed except in the case of bug fixes. Any stable ABI/API/config file format changes must be blockers. Note changes will be allowed to any files in the cts directory even if they are not blockers. Release 2.0.0 (needle) - Our standard ABI guarantee, (X guarantees on-wire and API/ABI, Y may add new features or new APIs, Z are bug fixes only), no serious blocker bugs making the software unusable. blockers - The software is unusable for Pacemaker, GFS, QPID, Sheepdog, or has some major flaw which prevents its general usability by other projects. The schedule: Alpha January 17, 2012 version 1.99.0 Beta January 31, 2012 version 1.99.1 RC1 February 7, 2012 version 1.99.2 RC2 February 14, 2012 version 1.99.3 RC3 February 20, 2012 version 1.99.4 RC4 February 27, 2012 version 1.99.5 RC5 March 6, 2012 version 1.99.6 Release 2.0.0 March 13, 2012 version 2.0.0 Once 2.0.0 is released, support for the 1.3 series will cease. Support for 1.4 series will continue for 3-5 years. Every patch from alpha+ must be verified to pass make dist and make rpm by the submitting developer. Regards -steve _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
