> On 29 Mar 2015, at 08:59, Ben Coman <[email protected]> wrote:
>
> - we try to have some issues tagged with “sprint” on the issue tracker..
> but this time it will be focused on bugs for Pharo4, I guess.
>
> but there will be not enough bugs.
>
> As well as trying to nail down the failing tests in the CI, there are some
> additional tests that only fail when TestRunner is driven from the UI. Could
> these be attacked?
>
That is one idea.
And there are many other bugs that we just pushed to later as not release
critical.
People can do other stuff, too, but of course we can’t integrate as Pharo5 has
not yet started… and I wonder if we
have the time to do that till then (to set everything up: CI..)
Marcus
