Justin Deoliveira wrote:
> Rob Atkinson wrote:
>> If the GSIP process takes so long, maybe we should have a single one
>> "fix everything" - seriously the effort that goes into breaking down
>> the big picture into small, regression testable changes needs to be
>> supported by a far more efficient
Rob Atkinson wrote:
> And in the meantime it sounds like Ben will have completed a local
> spike and be ready with the patch :-)
>
> If the GSIP process takes so long, maybe we should have a single one
> "fix everything" - seriously the effort that goes into breaking down
> the big picture into sm
And in the meantime it sounds like Ben will have completed a local
spike and be ready with the patch :-)
If the GSIP process takes so long, maybe we should have a single one
"fix everything" - seriously the effort that goes into breaking down
the big picture into small, regression testable changes
Understood; we also need to balance this with helping Ben through the hoops
:-)
I had a good skype session with Rob and Ben yesterday and I will try and
assist Ben as he documents what he intends to do.
Let us both try to review this page as it takes shape; I worry that we have
many different part
Hey Jody,
Up front I want to say that I realize we are putting this proposal
though many more hoops we do the standard proposal. But given 1) the
order of magnitude of the change and 2) the history of this topic, I
think the extra hoops are warranted.
So in terms of what I think the proposal n
Hi Justin,
I am going to restart the conversation on just this point - the proposal
needs to be more explicit in order for anyone to vote on it. What level of
detail are we looking for in this proposal; if this was design work we could
ask for nice class diagrams as per your catalog proposal. This
