Author: rhauch Date: 2009-06-09 12:36:50 -0400 (Tue, 09 Jun 2009) New Revision: 1013 Modified: trunk/docs/reference/src/main/docbook/en-US/content/future.xml Log: Updated the last chapter in the Reference Guide to better reflect the current status and plans for the immediate future. Modified: trunk/docs/reference/src/main/docbook/en-US/content/future.xml =================================================================== --- trunk/docs/reference/src/main/docbook/en-US/content/future.xml 2009-06-09 15:16:00 UTC (rev 1012) +++ trunk/docs/reference/src/main/docbook/en-US/content/future.xml 2009-06-09 16:36:50 UTC (rev 1013) @@ -31,21 +31,31 @@ <chapter id="future"> <title>Looking to the future</title> <para> - What's next for JBoss DNA? Well, the sequencing system is just the beginning. With this release, the sequencing system - is stable enough so that more <link linkend="sequencers">sequencers</link> can be developed and used within your own applications. - We've also established the foundation for JBoss DNA repositories, including a number of <link linkend="repository-connectors">connectors</link>. - We'll continue to expand our library of sequencers and connectors, as well as expand our support of JCR. - Other components on our roadmap include a web user interface, a REST-ful server, and a view system that allows domain-specific - views of information in the repository. These components are farther out on our roadmap, and at this time have not been - targeted to a particular release. + JBoss DNA &version; adds a lot of new features and capabilities. It introduced an initial RESTful server that makes + JCR repositories accessible over HTTP to clients. The JCR implementation was enhanced to support more features, + including the ability to define and register node types using the Compact Node Definition (CND) format. + A new configuration system was added, making it very easy to configure and manage the JBoss DNA JCR engine. + An observation framework was added to the graph API. The federation connector was rewritten to improve performance + and correct several issues. And quite a few issues were fixed. </para> <para> - If you're interested in getting involved with the JBoss DNA project, consider picking up one of the sequencers on our - <ulink url="http://jira.jboss.org/jira/browse/DNA?report=com.atlassian.jira...;. - Or, check out <ulink url="http://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=tru... - for the list of sequencers we've thought of. If you think of one that's not there, please add it to JIRA! + What's next for JBoss DNA? Passing all of the JCR API compatibility tests for Level 1 and Level 2, + plus some of the optional features, is the primary focus for the next release. Of course, there are a handful of + improvements we'd like to make under the covers, and a few outstanding issues that we'll address. + Farther out on our <ulink url="&Roadmap;">roadmap</ulink> are the development of additional connectors and sequencers, + some Eclipse tooling for publishing artifacts to a repository, and quite a few other interesting features. </para> <para> + We're always looking for suggestions and contributors. If you'd like to get involved on JBoss DNA, the first + step is joining the <ulink url="&Home;lists.html">mailing lists</ulink> or hopping into our chat room + on IRC (at irc.freenode.net#jbossdna). You can also <ulink url="&Home;subversion.html">download the code</ulink> + and get it building, and start looking for simple issues or bugs in our + <ulink url="&JIRA;">JIRA issue management system</ulink>. + </para> + <para> + But if nothing else, please contact us and let us know how you're using JBoss DNA and what we can do to make it even better. + </para> + <para> And, if you haven't already, check out our &GettingStarted; guide, which has examples that you can build and run to see JBoss DNA in action. </para>