On 07/21/2011 04:59 PM, Steven Dake wrote: > The Corosync flatiron 1.y series had many more features added then I > would have liked, but the development team feels the 1.y series > addresses any major gaps users of the software have had. As a result, > we are freezing any future feature development of the flatiron branch > permanently. We will continue to maintain z streams (1.4.z) bug fixes > for many years to come in a robust and aggressive fashion. > > Now that the flatiron chapter of Corosync is finished, we can move on to > new r&d work around Corosync 2.0. There are a few RFEs floating around > in bugzilla and the TODO list. This is your chance to provide feedback > about feature development you would like to see in Corosync. > > The overall theme for Corosync 2.0 is focused around trimming the fat > and simplifying the implementation without major performance regressions. > > The developers will take feature submission suggestions until Aug 31, at > which point we will prioritize features for 2.0 and close feature > submission requests. > > Regards > -steve
Might be worth linking to the TODO and a repo (wiki?) of existing RFE people have made, for others to review and comment on themselves. -- Digimer E-Mail: [email protected] Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "At what point did we forget that the Space Shuttle was, essentially, a program that strapped human beings to an explosion and tried to stab through the sky with fire and math?" _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
