On 10/17/06, Elias Torres <[EMAIL PROTECTED]> wrote:
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 gave you the impression that Allen and I were working against a code freeze of Friday last week. I was wrong (sorry about that). Our code freeze is the end of this week, which makes sense -- Thursday is "RC day" the second to last Thursday of the month according to the Roller Release Plan: http://rollerweblogger.org/wiki/Wiki.jsp?page=RollerReleasePlan
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.
That's fair. If we're going to work together we're going to have to plan together and stick to the shared plan. You've got the same right to vote down proposals that deviate unacceptably from the plan as we do.
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.
Read over that Release Plan and I linked to. Does it work for you and if not, what can we change/improve? One thing that we should address is the shared road-map, we don't have any plans past 3.1 on the wiki. If we can share some of our goals and requirements it should be easier for us to work together to meet them. - Dave
