Hi, just a suggestion from my experiences with JIRA and release cutting in Stanbol: The components in JIRA should correspond to the release artifacts that you are planning to cut. From our experience in Stanbol so far it makes things easier.
For example, you have LDCache and LDClient as components. Are those always released separately? If not, I would suggest to have only one component there. Essentially, it is this schema: - a JIRA component = release artifact - a JIRA version for a release can be defined as component-[version] - when cutting the release just check the resolved issues for the component This only applies if you want to release components independently. If you are planning to always release everything at once - it makes no difference. But I have to say that changing / editing components at any time is no problem in JIRA. So you can always change and shift the issues once a you found a structure that suits your needs. Best, - Fabian 2013/2/1 Sebastian Schaffert <[email protected]>: > I currently see the following additional components from what I've been > working on lately: > - Triple Store > - LDClient / LDCache > - Versioning > > > 2013/2/1 Sergio Fernández <[email protected]> > >> Hi, >> >> yesterday we discussed that the components does not fit with the (planned) >> project structure. Please, take a look on the current components at Jira: >> >> https://issues.apache.org/**jira/browse/MARMOTTA#** >> selectedTab=com.atlassian.**jira.plugin.system.project%** >> 3Acomponents-panel<https://issues.apache.org/jira/browse/MARMOTTA#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel> >> >> and send suggestion where we should go to more fine-grained. >> >> Greetings, >> >> >> On 17/01/13 10:13, Sergio Fernández wrote: >> >>> Hi, >>> >>> as you can see according the reports sent to the list the last days, we >>> consider the issue tracker a quite important infrastructure for any >>> software development. Therefore we spend some time settings Jira, for >>> instance about the components and the people responsible for each. Right >>> now are as follows: >>> >>> * Core: Core (Component Lead: Sebastian Schaffert) >>> >>> * Web Services: Web Services (Component Lead: Thomas Kurz) >>> >>> * Admin Interface: User Interface for administration of the system >>> (Component Lead: Thomas Kurz) >>> >>> * Build Environment: Maven build environment, dependency management and >>> packaging (Component Lead: Sebastian Schaffert) >>> >>> * Clients: Linked Data Client Library (Component Lead: Jakob Frank) >>> >>> * Libraries: Common Libraries (Component Lead: Sebastian Schaffert) >>> >>> * Extras: Extra stuff, such as integration with third-party tools >>> (Component Lead: Sergio Fernández) >>> >>> * Website: Web site (Component Lead: Sergio Fernández) >>> >>> * Dissemination: Publicity and project dissemination (Component Lead: >>> Sergio Fernández) >>> >>> Any comment or suggestion would be welcomed regarding this. >>> >>> Cheers, >>> >>> >> -- >> Sergio Fernández >> -- Fabian http://twitter.com/fctwitt
