-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 2:18 PM To: Avalon Developers List Subject: Re: [PROPOSAL] Adopting JIRA
Farr, Aaron wrote:
-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 2:06 PM To: Avalon Developers List Subject: Re: [PROPOSAL] Adopting JIRA
Farr, Aaron wrote:
Thoughts?
One more approach - create groups relative to maven GroupID (which would be closeish to the moderate approach you described). This means that we should be able to more simply automate project to JIRA links in our documentation.
I like the idea of tying it to Maven. Though that would result in a
project
list like this:
http://www.apache.org/dist/avalon/
right?
Umm - good point - that's way too many groups. Perhaps we should review project group ids as we move forward. E.g.:
cornerstone-xxx ---> avalon-components excalibur-xxx ---> excalibur avalon-xxx ---> avalon
Sounds pretty good. I'm a +1 on consolidating cornerstone-xxx and
excalibur-xxx since generally we do a Cornerstone release or an Excalibur
release (several components all at once).
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.
Fortress should be separate. It was originally excalibur-fortress and then moved to avalon-fortress. It should either stay there or move to just "fortress."
I would treat this exactly the same way we treat Merlin or Phoenix. I.e. a group identity in JIRA, and as we move forward with a new release we move the Maven group id to "fortress".
Cheers, Steve.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
