On Mar 28, 2007, at 1:04 PM, Henry Minsky wrote:

What's a good way to check if a change has been integrated already from legals to 4.x?

How do I count the ways?

They *should* be entered in

http://wiki.openlaszlo.org/4.0_Merge_Log

But I usually just scan my archive of laszlo-checkins email, which has all the chaff (builder checkins, patch checkins) filtered out.

Or you could look in websvn, but that service is down right now because of a DOS attack last night.

Or you could do

$ svn log --stop-on-copy http://svn.openlaszlo.org/openlaszlo/ branches/4.0 | more

and scan through looking for a revision range containing your revision.

Or you can ask Max, the merge manager.

jim



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]


Reply via email to