NOTE... the m2 build in trunk is already broken... this patches help
FIX MANY OF THOSE PROBLEMS!
Since the official build is still m1 and this will not affect the m1
build, I don't see why your point about breakage is applicable at all.
When I first created the m1 build for Geronimo years ago there were
certainly a few moments of breakage due to build changes, but since
there was no commit by committee junk going on then it was easy to
just fix when things happened to get a bit askew.
The branch idea was just to make it easier to actually make progress,
as I am move on this stuff way way faster than the lot of you can
react to emails and JIRAs which often (as this one did) need several
sets of emails to clarify.
:-(
--jason
On Jul 3, 2006, at 11:31 AM, Jacek Laskowski wrote:
On 7/3/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
I'm not following your line of thought when you mention experiments.
Can you provide more detail?
(It turns out that I'm a victim of my own English, and I can't express
my mind clearly.)
What I meant was to refer to our m2 efforts when it works for one and
does not for others and we can't figure out why. As many stated, it's
unacceptable to happen in trunk, which would've had if it'd done in a
conventional manner - CTR. Call it whatever you like - experiments are
what suited best for me, esp. while we're experimenting with m2 build
until we get to the point when it's ready to be applied to the trunk.
Rather than wasting Jason's time and encouraging him to follow RTC
rules, which add nothing but frustration and disgust, we could use a
solution that was indeed mentioned many times - a branch. It's like a
sandbox where we can do everything - experimenting - until we find the
one working solution ready for RTC.
(somehow I feel you read it otherwise, but again it might be that my
English's not working well)
Alan
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
