Release 0.3

[cbrnr]

@mbillingr, since we've implemented a lot of useful things since 0.2, I would like to release 0.3. Are there any outstanding issues before we can release 0.3?

[mbillingr]

There are still open issues in Milestone 0.3. I think we will not be able to do them all in the near future. Let's fix a date for the next release and what's in by then is in, unless there are any show-stopping bugs we need to fix. What do you think?

[cbrnr]

OK. Today? Let's move all open 0.3 issues and PRs to 0.4 - unless you have time for a few quick ones that you think must go into 0.3.

[mbillingr]

I'm not a fan of our current arbitrary hey let's release today strategy :)

Anyhow, I also don't have anything better to offer and everything seems to be stable at the moment, so why not...

But I'll not put it on pypy today.. that was too troublesome last time and I'll rather wait a few days to see if the release is going to stay.

[cbrnr]

Currently, it's the best strategy we have, because we cannot predict how much time we have to work on the toolbox.

I'll work on #124 today - let's include this one in 0.3 and then call it a release.

And yes, +1 for delaying the PyPI release a few days. We can't model zero-lag with a VAR anyway :-). What about releasing it next Monday?

[mbillingr]

You mean github release today and pypy on monday?

[cbrnr]

Yes