> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> >
> > But for Avalon, we have framework, meta, repository, utilities, etc.
> > They're all on different release schedules. But if we really want meta,
> > repository and utilities to be extensions of the framework, then they
> could
> > all be included under one group ID (and JIRA project).
>
> I'm not suggesting these for a single project. What we can do is to
> group a set of components together under JIRA group - and what I'm
> thinking is that we would have multiple JIRA Groups basically close to
> your Minimalist structure.
>
> Each group would then break out into a project per versionable artifact.
> I.e. avalon-framework-api is a project in JIRA under the Avalon Group.
Just to be clear, you mean have:
Avalon
Excalibur
Cornerstone
Merlin
Phoenix
Fortress
Be JIRA categories? And then have individual JIRA projects for each:
Avalon-xxx
Cornerstone-xxx
Excalibur-xxx
Hmmm... I don't mind the Avalon-xxx projects, but I think Cornerstone and
Excalibur don't need to be categories. Just a single JIRA project for each.
While the individual components may be different maven artifacts (and
currently under separate group IDs), we've often released them together,
i.e.- Cornerstone-1.0, Excalibur Release 1.x.
So I think I'm leaning towards starting with:
Avalon <-- framework + docs
Meta (or Avalon-Meta)
Repository (or Avalon-Repository)
Excalibur
Cornerstone
Fortress
Phoenix
Merlin
LogKit
All under a single Avalon category.
Sorry to drag this proposal out. Just want to make sure we get it right.
Do any of the JIRA experts want to chime in again? :)
J. Aaron Farr
SONY ELECTRONICS
DDP-CIM
(724) 696-7653
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]