The Server Side wrote:

New Components
Two new components were added to the RichFaces library with the current release, namely
<rich:editor> and <a4j:queue>. You can see the components in action on the "RichFaces live demo" (<rich:editor> and a4j:queue )web page.
Usage and implementation, design details are available in the RichFaces Developer Guide ("Queue Principles", "<a4j:queue>" and "<rich:editor> " ) and on the Jboss.org Wiki ("rich:editor component" and "Design of RichFaces <a4j:queue/>").

The Improved Queue
The <a4j:queue> component was introduced with this release. The component creates a queue of the Ajax requests. The Ajax4JSF or RichFaces components with built-in Ajax can reference the queue to optimize their Ajax requests.
The improved queue provides a number of advantages and broader flexibility, i.e. it:
* Eliminates the possibility of collisions when several JSF requests pass the JSF lifecycle at the same time. The queue prevents sending such requests. Only one request is processed. The rest ones are waiting.
* Reduces the traffic between browser and the server. The "similar" requests came within requestDelay are absorbed. Only the last one is actually sent. Reducing the number of requests in its turn reduces the server load.
The queue will help you optimize your Ajax requests traffic and reduce server load.

The <rich:editor>
The <rich:editor> component is an adaptation of TinyMCE WYSIWYG editor for JSF applications.
The key features:
* You don?t need to write any JavaScript code in your application to use the TinyMCE editor. You can define all TinyMCE ?s properties via attributes and the <f:param> JSF component specifying the name of the property in the "name" attribute and assigning the value with the "value" attribute.
* You could only once specify all configuration parameters (you need to use the ".properties" file to store the properties) for your editor, use the "configuration" attribute and pass the name of the configuration file to the attribute. You can also dynamically assign the configuration file name in runtime using EL expressions.
* You can add some custom plug-ins to the editor.
* TinyMCE ?s callbacks can be fired using <f:param> or using some event handler attribute.
* The implementation of the <rich:editor> provides a built-in Seam text converter.

febatata wrote:Alguém aí pode reportar sobre compatibilidade?
Estamos começando os testes para migrar a versão, principalmente pra poder usar esse editor que parece que ficou bom!

Queria saber aí o feedback do pessoal sobre a compatibilidade.