I would go for one JIRA project and the current versionning scheme for now, but this is not a strong opinion. I guess we can always split things if needed later (especially if the number of components grow).
2009/2/12 Gert Vanthienen <[email protected]>: > 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 > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
