+1 on the general concept, details to be figured out...
On 04/10/2013 09:55 AM, Justin Ross wrote:
Hi, everyone. We've recently been discussing the components of our project in a couple different contexts. This is a proposal to take the outcomes of those discussion and apply them to how Qpid is organized.
[snip]
## JIRA instances We propose *not* to create new jira instances for each component. We can do that later on if necessary. For now we can overload the version field in the qpid jira instance to include a component name.
"Overload the version field" sounds like a Bad Idea to me. That's not what the version field is for. Anyone know of projects that have successfully done this? I would say that if a component is big enough to have its own SVN repo, then it's big enough to have its own JIRA. Note that the only successful component to date (Proton) /does/ have it's own JIRA. Anyone think it's a good idea to merge the Proton JIRA into the QPID JIRA?
Cheers, Alan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
