The system I am currently using maps "sub-projects" as JIRA project
components, but this away the possibility of having independent
releases. All sub-projects must be released in one go. If a sub-project
evolves slowly relative to the other sub-projects, it will have
redundant releases, but this is not too bad.
I tried "JIRA project per component" system, but that led to
proliferation of too many projects and that became difficult to manage.
I needed to initiate "re-unification" processes.
scott.stark(a)jboss.org wrote:
With the breakup of monolithic projects like commons, and soon mc,
what is the best way to manage the subproject artifact releases? The subprojects could be
made top-level jira projects, or we could just create releases for each subproject as
needed. I guess I prefer the latter rather than introducing too many small projects.
I don't suppose jira has any support for subprojects and artifacts?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058361#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...
_______________________________________________
jboss-dev-forums mailing list
jboss-dev-forums(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-dev-forums