On Sun, Nov 7, 2010 at 3:16 PM, Peter Muir <pmuir@redhat.com> wrote:
The brevity and purpose of the Seam30Roadmap must not be compromised, it must show an easy to understand overview of the current status of modules and their target dates. If you can cut most of the waffle from the other page I guess they can be consolidated.

Got it. When I get a chance, I'll see if I can come up with a proposed layout that will fit this requirement.


Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597