[seam-dev] Seam JIRA for Seam 3

[Dan Allen]

On Wed, Mar 10, 2010 at 6:57 AM, Pete Muir <pmuir at redhat.com> wrote:

> All,
>
> As we split Seam into modules (and as some like remoting and XML approach a
> beta release), we need to consider how JIRA should look for Seam 3.
>
> We plan to release modules independently, with a "feature-boxed" lifecycle,
> releasing modules either as features are added, or critical issues arrive.
> We also plan a "bundle release" at regular intervals, which takes all the
> modules, and provides a single stack that are tested to work well together.
>
> Keeping JIRA simple and monolithic has the advantage of being easy to
> understand and point people at. We can use components to track a module. We
> would have to prefix the version with the module name, and tracking issues
> to releases becomes pretty difficult.
>
> Using a JIRA project for each module allows much cleaner tracking of issues
> to releases.
>
> I favour the latter, but am interested in others opinions.
>

As do I. When I file bugs (or review them), I prefer as much granularity as
possible. Otherwise, searching and filtering is just too much effort.

-Dan

-- 
Dan Allen
Senior 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20100310/695fb278/attachment.html