13422 Debugger disabling fix
Hi, What are the next steps for 13422 (and 13451)? Can it be integrated and a new build for 3+4 made? Do we need to wait for the monkey? The earlier slice in 30851 breaks a.o. the GTDebugger in Moose, so the latest version of the slice is now added by hand to the moose ci. Stephan
On 09 Jul 2014, at 11:47, Stephan Eggermont <stephan@stack.nl> wrote:
Hi,
What are the next steps for 13422 (and 13451)? Can it be integrated and a new build for 3+4 made? Do we need to wait for the monkey?
The monkey sadly has some problems (related to the Context cleanup somehow), its on my list but not yet fixed. Therefore:
The earlier slice in 30851 breaks a.o. the GTDebugger in Moose, so the latest version of the slice is now added by hand to the moose ci.
I will integrate the Pharo4 fix now, and of it works the back port after. Marcus
Thanks, Marcus. Doru On Wed, Jul 9, 2014 at 12:56 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On 09 Jul 2014, at 11:47, Stephan Eggermont <stephan@stack.nl> wrote:
Hi,
What are the next steps for 13422 (and 13451)? Can it be integrated and a new build for 3+4 made? Do we need to wait for the monkey?
The monkey sadly has some problems (related to the Context cleanup somehow), its on my list but not yet fixed. Therefore:
The earlier slice in 30851 breaks a.o. the GTDebugger in Moose, so the latest version of the slice is now added by hand to the moose ci.
I will integrate the Pharo4 fix now, and of it works the back port after.
Marcus
-- www.tudorgirba.com "Every thing has its own flow"
participants (3)
-
Marcus Denker -
Stephan Eggermont -
Tudor Girba