Noel J. Bergman wrote:
IMHO just ask infrastructure@ (ie Noel :D) to create an Avalon project.

Absolutely not. I am the least experienced of the Jira admins. About the only reason I got involved in the first place is because I am root on the server that houses it. If you want to give credit where it is due, Serge is the one who took the initiative to bring Jira to the ASF, and is probably the most experienced Jira person we have here.

Bah. Thanks, I may have started it, but Noel has done much more work than I have.


if every TLP has a dozen projects the jira will be difficult to
navigate

You don't need to see everything in Jira. Just configure your dashboard fot the projects you want to track. In the case of something like Avalon, if there was a request to create Merlin, Frameworks and whatever, we could create an Avalon program category, and then you could use the category portlet to select the Avalon projects.

You will want to create a separate project for each product you want to release. The motivation for this is that JIRA can easily create changelogs and roadmaps based on versions (changelogs = issues assigned to a released version, roadmaps = issues assigned to an unreleased version).


JIRA can group these into a "project group" so you can restrict your view that way.

I expect that a permission scheme would be created for the Avalon projects,
with a group used to identify the project's participants.

Yes, as Noel suggested, initially for Avalon I expect to have a single group and permission scheme that will be shared by all Avalon projects.


--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to