----- Original Message -----
Sent: Wednesday, August 30, 2006 10:02
AM
Subject: Re: [Laszlo-dev] buildlfc
broken,let's use ant (was Re: For Review: Change change.mpn1DMMUq.txtSummary:
Back out changes merged from trunk - buildlfc works again)
OK, chatting with Ben a bit, here's a plan:
- We reopen LPP-2118 against 3.4, and ask QA to look at all the scripts
that might have been affected by the checkin to trunk. This is because
buildlfc is broken on OS X in trunk as well (which means it is likely broken
on 3.3.3 too). I've done this and assigned the bug to Mamye, who will
determine who on the QA team handles it.
- We file a new bug (done: LPP-2585) against Legals to make sure the
original spaces-in-pathnames-on-Windows bug is fixed the right way
there.
- We resolve LPP-2576 by Max backing out the change as originally
planned.
So Max: with regard to your email "Change change.mpn1DMMUq.txt Summary:
Back out changes merged from trunk - buildlfc works again", you have my
approval as the QA reviewer :-) Let me know when the change is checked in and
I will migrate it to branches/legalspr3.
jim
On Aug 30, 2006, at 8:16 AM, Jim Grandy wrote:
On Aug 30, 2006, at 5:16 AM, P T Withington wrote:
Please take great care in this area. The LFC build mechanism is
significantly different between trunk and legal's due to the
addition
of multiple runtimes.
I would not expect a blind integration from
trunk to legals to work.
But blind integration is exactly what we did. This would argue for
returning to Max's original plan and reverting the change to fix the
spaces-in-pathnames problem on Windows. For Legals, at least, LFC
productivity is currently of paramount importance; we can live with the
spaces-in-pathnames problem for a little while longer on Windows.
(Of course, we should create a Legals copy of the original bug so that
we remember to address it.)
If folks agree, I think this one is back to Max for the original
reversion fix.
jim
_______________________________________________
Laszlo-dev mailing list
_______________________________________________
Laszlo-dev
mailing
list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
