> A "project" in JIRA is something with a version lifecycle.
Correct.
> A "component" in JIRA is not a component in our sense of the
> work
A component is anything that you want to assign its own little catagory
within the realm of a versionable item. This also has a relationship to
Subversion, since the issue of where to place the /[braches, tags, trunk]
structure is dependent upon what is a releasable/versionable entity.
Jakarta Commons, for example, would have many Jira projects. James has two:
the James server and jSieve (three if we count the web site, but for the
moment that is bundled in elsewhere). I would not be in favor of separate
versioning, for example, for each of our mailets, although technically they
could be released seperately. Nor is each HTTPD loadable module made
available separately.
So if Merlin is the releasable entity, it is a Project, and it has branches,
tags and trunk. If some of those things are not separately
versioned/released, they should not be separate Jira projects. And if the
Avalon PMC looks at the number of releasable components and decides that
Cornerstone (for example), should be put out as one unified release, that is
a decision it can make. Just because things can be seperated, does not mean
that you have to release them that way.
The Project Category is used to aggregate project's for the dashboard. I
think that we all agree that improved organization tools within Jira are
desirable.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
