[Pharo-project] [TODO] 1.2 Core + Full
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/lastCompletedB... 18 of 10284 tests fail: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/te... 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%... 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&co... All failing tests do have bug-tracker entries. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Hi Marcus, Thanks, your mails are good to push me ahead ;-) I think that #3455 is ready for integration (make 2 tests pass in dev). and #3447 too (provided CS or just remove the method). #Luc 2010/12/22 Marcus Denker <marcus.denker@inria.fr>
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/lastCompletedB...
18 of 10284 tests fail:
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/te...
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%...
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&co...
All failing tests do have bug-tracker entries.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On Wed, Dec 22, 2010 at 9:18 AM, Luc Fabresse <luc.fabresse@gmail.com>wrote:
Hi Marcus,
Thanks, your mails are good to push me ahead ;-)
I think that #3455 is ready for integration (make 2 tests pass in dev). and #3447 too (provided CS or just remove the method).
Luc, in the cae of 3447, you should commit to the Shout repo since this is not part ofpharo core. BTW....which version of ShoutWorkspace was being installed...because I already fixed that in: Name: ShoutWorkspace.1-maiano.6 Author: maiano Time: 12 May 2010, 7:53:35 pm UUID: 8265a4c8-d212-4ac1-b2d5-79b5722ed9c3 Ancestors: ShoutWorkspace.1-Alexandre_Bergel.5 Removed menuCommandOn: aBuilder from ShoutWorkspace as such item is already in the manu (in the part of most common tools) together with SystemBrowser, Test Runner and Monticello Browser. If they are not there, then they are not under "Tools". cheers mariano
#Luc
2010/12/22 Marcus Denker <marcus.denker@inria.fr>
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/lastCompletedB...
18 of 10284 tests fail:
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/te...
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%...
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&co...
All failing tests do have bug-tracker entries.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Yes I will help too. On Dec 22, 2010, at 8:07 AM, Marcus Denker wrote:
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/lastCompletedB...
18 of 10284 tests fail: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/te...
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%...
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&co...
All failing tests do have bug-tracker entries.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Ok, I check the one on MessageTally Alexandre On 22 Dec 2010, at 04:07, Marcus Denker wrote:
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/lastCompletedB...
18 of 10284 tests fail: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/te...
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%...
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&co...
All failing tests do have bug-tracker entries.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
One test fixed: http://code.google.com/p/pharo/issues/detail?id=3476 Also, it would be cool to have our test on the debugger: http://code.google.com/p/pharo/issues/detail?id=3442 It run green. It is tagged Milestone-1.3. Why not to include it in 1.2? Cheers, Alexandre On 22 Dec 2010, at 04:07, Marcus Denker wrote:
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/lastCompletedB...
18 of 10284 tests fail: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/te...
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%...
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&co...
All failing tests do have bug-tracker entries.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On 22/12/10 2:07 AM, Marcus Denker wrote:
23 reports are tagged as 1.2: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2&colspec=ID%...
The fix/test for Issue 3452 http://code.google.com/p/pharo/issues/detail?id=3452 should be included. Otherwise, a patch would be needed to load Glorp.
participants (6)
-
Alexandre Bergel -
Luc Fabresse -
Marcus Denker -
Mariano Martinez Peck -
Stéphane Ducasse -
Yanni Chiu