For 1.2 to to be released, we need to
a) get all tests green.
There are right now 9 failing tests in Core and 9 additional one in the full image.
� � � �9 of 7915 tests fail:
� � � �https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompletedBuild/testReport/
� � � �18 of 10284 tests fail:
� � � �https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/testReport/
some of those are test-server artefacts that only fail on the testserver.
b) Bug Tracker. Here the issues need to be either resolved or decided to be not show-stoppers
� �(there will be a 1.3 release! So somehting that is already not in 1.1, why do we need in in 1.2?
� � A release is just a usable snapshot of an on-going process)
23 reports are tagged as 1.2:
� � � �http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
8 reports are tagged as 1.2 for the full image?
� � � �http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
All failing tests do have bug-tracker entries.
� � � �Marcus
--
Marcus Denker �-- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.