I think it's important to ensure an individual module page exists for every
module listed as required. Setting up a module page is the responsibility of
the module lead, though of course we are here to help.
I know this seems like extra work, but without a page your module really has
no identity, other than the source code. The module page just says:
- hello, I exist
- this is why you should care
- this is who's working on it
- this is where the resources are
Some module pages are more details than others. It's up to you to decide to
what extent to use the page. You can set the roadmap on the module page or
through JIRA. Again, up to you. What's important is that the module page
exists.
Instructions for how to set it up are provided in the module handbook:
http://seamframework.org/Seam3/ModuleInfrastructure#H-ModulePage
-Dan
On Thu, Oct 21, 2010 at 11:24 AM, Pete Muir <pmuir(a)redhat.com> wrote:
After last weeks IRC meeting, I now have a good understanding of
where
modules have got to.
http://seamframework.org/Seam3/Seam30Roadmap
Headlines:
* Aiming to get most modules to beta by end of Oct. A few (security,
persistence, drools) likely still in alpha
* Beta of Seam 3 by 12th Nov in time for Devoxx
* Second beta in early December with all modules at beta
* First release candidate in early January
All module leads, please look at the roadmap and check that you can get
your module to beta by then.
Ken, Shane, Jozef, still need to hear from you about when you can get
International, Security and REST to beta -- please ping me.
Pete
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen