I've been with Roller for sometime now but it is until recently that I have been working closely with to the development lifecycle. At the end of 3.0 we submitted proposals for working on 3.1 and those got approved so we are making plans based on those proposals and dates estimates. However, there have been a couple or more proposals that appear last minute before code freeze and get submitted/implemented. I'm just trying to figure out our process and what's good practice and what's not. I'm not sure how would you feel if I submitted a few proposals this week on behalf of IBM's needs as opposed to waiting for 3.2. I'm not saying that we can't work like this, but I'm trying to understand what is acceptable or not to this community. I definitely don't want to misbehave in the friendly/cooperative environment we have today.
As I look into the future of IBM and Roller I'm not sure we'll have tons of proposals closely tied to the schedule because we won't be able to keep up with Roller's short lifecycle. Our direction is going to be more like: get a feature implemented in whichever release it happens to fall under and we backport it to our internal version until we make the jump to let's say 4.0. -Elias
