Latest Build added items that are not yet set as "to include"

Yes I always take time to close them to be sure that everything is integrated :)
Tx for the warning.

The latest build #50365 added two Issues (#16722 and #15162), but in Fogbugz these are still under review by the Monkey, and not set as “to include”.

 

 

Best regards,

Henrik

but it would be good to put them on “to include” before integration. This way we do not do double work

Just relax and trust me. It would help me.

They were tested already. I checked that.
The problem is that the monkey is restarting to check because I did not close them fast enough.

Yes I always take time to close them to be sure that everything is integrated :)
Tx for the warning.

Le 6/10/15 10:17, Henrik Nergaard a écrit :

The latest build #50365 added two Issues (#16722 and #15162), but in Fogbugz these are still under review by the Monkey, and not set as “to include”.

 

 

Best regards,

Henrik

I thought that I did it so may be I did it on the wrong issue.
Now it would be nice if you could get much nicer with people spending their time to improve
Pharo. You are not the only one looking at bug and improving pharo.

Stef

On 06 Oct 2015, at 10:45, stepharo <[hidden email]> wrote:

Just relax and trust me. It would help me. 

that’s not the point. It is about communication. And exactly about that:

They were tested already. I checked that.
The problem is that the monkey is restarting to check because I did not close them fast enough. 

Exactly that does not happen if you put the issue on “fix to include”. It’s not hard to do and solved

many problems. Why not do it?

Le 6/10/15 10:34, stepharo a écrit :

Yes I always take time to close them to be sure that everything is integrated :)
Tx for the warning. 

Le 6/10/15 10:17, Henrik Nergaard a écrit :

The latest build #50365 added two Issues (#16722 and #15162), but in Fogbugz these are still under review by the Monkey, and not set as “to include”.

 

 

Best regards,

Henrik