Jacek Laskowski wrote:
On 7/5/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
I'm afraid that I have to agree w/ Aaron here Jacek. I'm not sure that
there was a consensus on this. If discussion died down on this it was
because it's the 4th of July.
Ok, you *might* be right, but should I vote for creating a branch for
the work I think should be done in a branch? AFAIR, a branch doesn't
need a vote, does it?
I understand I could've been read as ignoring Aaron's points, which I
didn't mean to have done. I do appologize for it.
No worries. :)
To be sure a branch doesn't need a vote. But this is a different
situation. Multiple people are working on getting this done, it's not a
the sandbox effort of an individual, e.g. Jan's servlet stuff or David's
JACC stuff.
Discussions are still going on and I have proposed that working in trunk
on m2 still follows the RTC mandate in that m2 is not being used yet.
Once the m2 team is happy w/ what we have, an RTC can be formed. Any
minor changes, I don't fore see the need, that need to be done along the
way can be handled with RTCs. Working in this manner has the added
benefit of limiting the scope of the effort to just getting m2 working.
Regards,
Alan
