Hello,
*1) I asssume that my task is to test it? If the test would be ok, should I click on resolve in Fog Buz?* So basically when you resolved your bug, you added a slice and put the status fix review needed. Then, the monkey (which is a script) took the latest pharo image, added your slice and ran all the tests. If all the tests of the image passed with your new slice (which is the case), the monkey put the status Fix reviewed by the monkey, that you have now, and this means your fix does not break any test in the image. If your slice had broken tests, the monkey would have put back the status to Work needed. So you do not have to do anything right now. Someone will have a look to review your code and put the status to fix to include (but this should not be you), this reviewing step is sometimes skipped (it is usually skipped when the fix is minor or obvious). Lastly, an integrator (usually Marcus, but it could be Esteban or Stef) will integrate it. Your fix should be integrated in the next few days if the code review is ok. *2) I downloaded Pharo 3.0 but after selecting the Class Date in the Browser, I get an emergency evaluator, so I can not test it. Perhaps not yet time totest? Wait? Is the emergency evaluator reason interesting for you?* No clue. I tried and I had no emergency evaluator. By browser you mean Nautilus right ? 2013/11/8 Sabine Knöfel <[email protected]> > Hi, > > I got the Fog Buzz message below. > > 2 Questions: > > 1) I asssume that my task is to test it? If the test would be ok, should I > click on resolve in Fog Buz? > 2) I downloaded Pharo 3.0 but after selecting the Class Date in the > Browser, > I get an emergency evaluator, so I can not test it. Perhaps not yet time to > test? Wait? Is the emergency evaluator reason interesting for you? > > I want to contribute:-) please tell my how :-) > > Regards > Sabine > > ############################## > A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. > > Case ID: 11222 > Title: Date readFrom:pattern: (year 2 decimals not 20xx but 00xx) > Status: Resolved (Fix Reviewed by the Monkey) > Category: Bug > Project: Chronology > Area: 1. Pharo Image > Priority: 5 - Fix If Time > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Sabine Knöfel > > URL: https://pharo.fogbugz.com/f/cases/11222 > > > Changes: > Added tag 'Validated in 30555'. > > > > -- > View this message in context: > http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp4720186.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >
