What's a good way to check if a change has been integrated already from legals to 4.x?
On 3/28/07, Max Carlson <[EMAIL PROTECTED]> wrote:
Let me know what you want to do with r4518. Henry, don't forget to send a migration proposal out for your recent changes. The other ones are in. Mamye, can you spin another 4.0.x build? Jim Grandy wrote: > r4515, yes. r3758, sounds a bit risky. Anything we can do to test around > that change to see if anything was broken? > > jim > > On Mar 27, 2007, at 8:08 PM, Max Carlson wrote: > >> I think we should take these... >> >> P T Withington wrote: >>> Revision: 4515 >>> Bugs Fixed: >>> LPP-3779 'Misleading Compilation exception syntax error' >>> Risk: low -- numeric attribute values follow same compilation path as >>> expressions now >>> Reward: User-reported bug >>> Revision: 4518 >>> Bugs Fixed: >>> LPP-3758 'Java stack trace while compiling malformed JavaScript code' >>> Risk: low-medium -- Somewhat complicated changes were required to the >>> parser/compiler interaction to get proper source information for >>> errors in DHTML >>> Reward: User-reported bug >> >> --Regards, >> Max Carlson >> OpenLaszlo.org > -- Regards, Max Carlson OpenLaszlo.org
-- Henry Minsky Software Architect [EMAIL PROTECTED]
