[Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Marcus Denker-4
Hi,

We have 40 issues that are tagged for Pharo6:


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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Henrik Sperre Johansen
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-basicIdentityHash-MUST-be-defined-in-every-immediate-class

(I imagine the same fix would be beneficial on Pharo7 as well, btw)

Cheers,
Henry
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Henrik Sperre Johansen
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
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Marcus Denker-4

> On 25 Aug 2017, at 15:47, Henrik Sperre Johansen <[hidden email]> 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





Reply | Threaded
Open this post in threaded view
|

Re: [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Marcus Denker-4

On 25 Aug 2017, at 15:50, Marcus Denker <[hidden email]> wrote:


On 25 Aug 2017, at 15:47, Henrik Sperre Johansen <[hidden email]> 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.


Marcus



Reply | Threaded
Open this post in threaded view
|

Re: [Pharo6] [Issue Tracker] Help Needed: issues tagged Pharo6

Stephane Ducasse-3
In reply to this post by Henrik Sperre Johansen
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
<[hidden email]> 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-tp4964056p4964077.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>