Re: [seam-dev] Seam JIRA for Seam 3

People,

We still need an issue tracker for tracking common Seam tasks: * Build infrastructure * Common documentation * Shared examples * Simultaneous release tasks * A dumping ground for "new-users" to put issues which they don't know where they belong (it's then up to us to triage them to the correct place). As we've diverged so much from Seam 2, I propose we create a new project in JIRA, SEAM, and keep JBSEAM for Seam 2 issues. This should reduce cross-over confusion between the two codebases' issues. It also has the nice sideeffect of allowing us to get rid of the unneeded JB prefix ;-)