Towards 0.4.0

[eblanca]

Do you see any blocking point to be fixed before 0.4.0 release?

[njh]

I would really like to test the tests passing again before making a release.

But other than that, there shouldn't be anything blocking a new release.

[eblanca]

I see in other projects hosted on github, when they're approaching a new release a new dedicated branch is created, so the main development may go on on 'master' branch, while at the same time the branch next-to-release remains untouched (and may only receive some fixes now and then).
May this be the case for twolame also?

[njh]

I don't think twolame is a big enough/complex enough project to merit multiple branches.

I have just fixed the build by disabling a test in e65a97a

I am also adding some items from my personal todo list to the Github issue tracker.

[njh]

I have marked all the issues that should be resolved before version 0.4.0:
https://github.com/njh/twolame/milestones/v0.4.0

Other issues have been marked v1.0.

[njh]

Three issues remaining (including this one!)