I personally favor a Jira for each component, but I agree that it is not realistic right now. I think its OK to start with large project for all components for now and maybe we can evaluate options later. I think the most important part is to document the individual comopnent releases very well and possibly add release information to the individual component pages in the wiki.
Chris -- Chris Custine My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org On Thu, Feb 12, 2009 at 10:31 AM, Gert Vanthienen <[email protected] > wrote: > L.S., > > If we look at the ServiceMix 3 JIRA project, the list of releases in there > is getting very long and very hard to work with. I know we discussed this > before, but I really think it makes sense to make a separate JIRA project or > projects for the components now. > One solution would be to create a single JIRA project for all the > components. Because we can release components independently, the version > numbers on the components will be going out of sync. One way to handle > this, is by using the same versioning scheme as we are using now in SMX3, > e.g. servicemix-ftp-2008.01 for version 2008.01 of servicemix-ftp. On the > other hand, we could also just create plain version numbers like 2009.01 and > then keeping the release open in JIRA until all components have reached that > version. > > The other way to get passed this would be to create a JIRA project per > component. This way, we could use versions in JIRA just as we are used to, > but the overhead of setting this up would be quite big. > > Which solution would people prefer? Are there any other suggestions for > solving this? > > Regards, > > Gert > >
