Page 2 of 2

Re: Remaining issues for 3.3.0

PostPosted: June 5th, 2020, 7:21 am
by Flint1b
Brent Easton wrote:You might be interested in looking at Bug 12850 which is a good follow on from the PieceMover issue.


I had a look, understood the general problem, messed around with the game piece layer settings in the editor, read the help pages on it, think I understood the principle of how it is supposed to work. Certainly an interesting bug to tackle. Now I'm having problems with creating a simple module to reproduce this, I asked about this in another thread.

Re: Remaining issues for 3.3.0

PostPosted: June 9th, 2020, 12:29 am
by Tim M
Cattlesquat wrote:I think 12551 is still waiting to be cleared through moderation?


Bugs dont go through site moderation

Re: Remaining issues for 3.3.0

PostPosted: June 9th, 2020, 1:58 am
by Cattlesquat
There's *some* kind of moderation, as they all start off "locked".

Re: Remaining issues for 3.3.0

PostPosted: June 9th, 2020, 10:27 am
by uckelman
Thus spake Cattlesquat:
> There's *some* kind of moderation, as they all start off "locked".

There is. The reason for it is to help with sorting out bugs from the
automatic bug reporter. I intend to look into what the other options
are for settings this evening.

--
J.

Re: Remaining issues for 3.3.0

PostPosted: June 14th, 2020, 10:53 pm
by uckelman
Thus spake Flint1b:
> Also, which bugs are still open and unassigned? I would like to fix
> another one, preferably one of those very difficult ones that need a lot
> of analysis and many hours of tracing through the code, those are my
> favorite.

I'm the default assignee, but if a bug is in status NEW and assigned to
me, that very likely means I haven't looked at it. (Why yes, I would
like this to work differently. It's an irritating consequence of our
SSO setup.)

--
J.