[Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6
Hi, We have 40 issues that are tagged for Pharo6: https://pharo.fogbugz.com/f/filters/1192/6-0-All <https://pharo.fogbugz.com/f/filters/1192/6-0-All> We should move as many of those to âLaterâ, so that we can focus on important fixes and back ports⦠sadly here we need to be realistic: We can not fix everything or even back port everything⦠we need to prioritise. It would help if people could âhelp decidingâ which issues do not need the Pharo6 milestone. Marcus
What's the point? Even if an issue has slice attached, is marked as Fixed, and has no failing tests in a local image, it'll be thrown out by a broken monkey / integration process, ref. for example https://pharo.fogbugz.com/f/cases/20119/basicIdentityHash-and-only-basicIden... (I imagine the same fix would be beneficial on Pharo7 as well, btw) Cheers, Henry -- View this message in context: http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6-... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Less crassly, what I meant to say, was; it'd be really nice if the integration process was fixed before too much energy is spent trying to backport/solve reported issues. Cheers, Henry -- View this message in context: http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6-... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 25 Aug 2017, at 15:47, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
Less crassly, what I meant to say, was; it'd be really nice if the integration process was fixed before too much energy is spent trying to backport/solve reported issues.
Yes, you are right⦠the strange thing is that the problem was introduced very late and we do not yet really understand what it is⦠(And I kind of suppressed my knowledge about it⦠just rememberd it when I tried to check a back port and it failed). Marcus
On 25 Aug 2017, at 15:50, Marcus Denker <marcus.denker@inria.fr> wrote:
On 25 Aug 2017, at 15:47, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
Less crassly, what I meant to say, was; it'd be really nice if the integration process was fixed before too much energy is spent trying to backport/solve reported issues.
Yes, you are right⦠the strange thing is that the problem was introduced very late and we do not yet really understand what it isâ¦
(And I kind of suppressed my knowledge about it⦠just rememberd it when I tried to check a back port and it failed).
I added an issue tracker entry. The very odd thing is that this test does *not* fail when you run it, it does not fail when run as part of the image tests when doing an update, either. https://pharo.fogbugz.com/f/cases/20339/Pharo6-test-runs-for-CI-fail-with-st... <https://pharo.fogbugz.com/f/cases/20339/Pharo6-test-runs-for-CI-fail-with-st...> Marcus
Oh yes :) Esteban is fully aware of that because you cannot imagine the amount of energy we are losing. On Fri, Aug 25, 2017 at 3:47 PM, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
Less crassly, what I meant to say, was; it'd be really nice if the integration process was fixed before too much energy is spent trying to backport/solve reported issues.
Cheers, Henry
-- View this message in context: http://forum.world.st/Pharo6-Issue-Tracker-Help-Needed-issues-tagged-Pharo6-... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (3)
-
Henrik Sperre Johansen -
Marcus Denker -
Stephane Ducasse