[Bigbang-dev] Please help test and debug

[Sebastian Benthall]

Hello,

I've been trying to hack away at the 0.2 tickets in preparation for the
IETF workshop.

What I've found is that there's quite a bit of maintenance work to do just
to get core functionality in a fresh build.

The reason for this is that we are not pegging our dependencies to specific
versions. When the APIs of the underlying dependencies change, that breaks
our code.

There are pros and cons to this. The con is that our code is broken. The
pro is that this forces us to do some mainenance work that should refresh
our understanding of how things fit together.

I'm doing what I can to chip in before the workshop, but I have to call on
you all to help out with:

- Testing! Trying to run each notebook and making issues for any failures.

- Debugging. Making pull requests to fix bugs. Ideally, these would include
an automated test that would catch related problems in the future.

You all have a better sense of what you're hoping to accomplish at IETF
than I do, but I would guess that smooth installation and working notebooks
is going to be key to getting people interested.

Cheers,
Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20180307/5befaae8/attachment.html>