On 20.08.2007 15:08 Uhr, Grzegorz Kossakowski wrote:
Let's forget about independent releases. Take a look at COCOON-2091[1] issue, it has Fix version set to 2.2. Now if some user would like to take advantage of Xinha should start to search Maven repository for org.apache.cocoon:cocoon-forms-impl:2.2 right? The answer is: no. It should start to search for cocoon-forms-impl:1.0.0-RC2 or cocoon-forms-impl:1.0.0. Our 2.2 is almost completely useless because it only carries one information: this change does not affect 2.1.x branch, nothing more.
This can be easily fixed by adding 1.0 to the list of versions. That's not really an issue, the actual one is to select the correct version from a big list.
I really wouldn't like to be seen as crazy person blindly pushing us to this split up. To be honest, I would like to do nothing. Such split up is lots of work in JIRA itself, then fixing URLs in our poms, etc. My goal is simple: let our issue tracking have valid information about version particular issue affects and version where particular issue is fixed.
You are not the only person. I'd prefer a better solution as well, but I change the camp since it does not seem to be worth the effort at the moment. You only move the problem from selecting the right version to selecting the right Jira project - and therefore break all the URLs. Some like issues linked in Jira comments themselves you can't even fix.
I think in the meantime we should just leave it as is and hope for improvements in Jira itself like versions specific to components and not only projects.
WDYT? Joerg
