Richard Tibbles

We have deprecated support for IE11 in 0.16, and will be dropping support in 0.17, so I am closing this as wontfix.

When implementing this, we should double check the implications for the final Kolibri WHL file size.

Yes, although I think the completely general case would need to be done in the KImg component in the Kolibri Design System - resolving this issue would mostly be managed...

Note that this is targeted for a 0.16 patch, so you should branch from the release-v0.16.x and target any PR there to avoid issues. We may take a little time...

This is resolved by the ability to flag the completion criteria as "set by content".

Another minor tweak here is that we can't prefix all the packages with `kolibri`, as eslint plugins and browserslist configs have very specific naming requirements, which is why they are...

Our plan had been to enable this workflow by pushing prereleases to the kolibri-proposed ppa, would this be fit the bill?

Hrm, yes, I think that should be feasible, now that I think about it, at least for the deb, the whl file probably wouldn't like that name.

How would you feel about `kolibri-deb-next` to go along with `kolibri-deb-latest`? That would seem like the simplest naming scheme to me.

Some of this should be addressed by some of the 0.16 work, the rest we can further triage to 0.17.