i understand the concerns (at least i think). but i don't see a way on how to make open source development more predictable. at least not the amount of work we try to do with the amount of resources we got. we don't have management resources, which in our case works just fine because all the contributors are educated enough. it's efficient, but not so predictable. the biggest problem is that curently i make the selection of issues when i start working on them. so then i make a decision based on all the latest priorities. when i would do this before and document this properly in jira, priorities will probably shifted by the time i start working on them and the result would be the same kind of unpredictability but more overhead in jira. currently i use jira as a set of post its. i put them on the next release where i think i should have a look at them. if at that time i decide to postpone, i just move the release date. that is what is going to happen with the 3.2 jira issues. a number of them have already been fixed. another bunch will be postponed and a third part will still have to be fixed. anyways. thanks for the feedback (and your patience:-). at least i know better your concerns. i'll try to find ways on how we can make the dev process more predictable. i hope this background gave you some insight in the why the current model is not so predictable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022926#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...