Re: [seam-dev] Seam JIRA for Seam 3
funny - I would hate having to track down progress across this many jira projects (thats
one area where jira sucks).
In JBoss Tools we currently run a mixed model to avoid too much fragmentation, i.e. JBIDE
has *all* components listed for easy bugreporting but a few of them (jbpm, drools, ..)
have separate jira because of different release cycles.
Would I like to go to project per module ? Yes, but not until jira gets cross-project
tracking and that we don't have to coexist within a UI that lists 50+ projects that
all start with the same prefix
Not saying, your decision is wrong - just saying i'm looking forward to hear how it
goes.
/max
On Mar 10, 2010, at 12:57, Pete Muir 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.
Pete
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev