Release 0.4?

[IanButterworth]

0.4 has sat on master since we stalled the release JuliaRegistries/General#5939

There have been a number of beneficial changes since, so it would be good to put out a release.

Also, with #61 upcoming, it would be good to get a stable release before that merges

cc. @andrewadare @mgkuhn @samuelpowell

[samuelpowell]

@ianshmean can you remind me why we stopped that registration?

@andrewadare any objections to releasing 0.4, I'm happy to do it.

[andrewadare]

I do not have any objections to releasing version 0.4. I also think we should get #61 merged and make a release from that. That PR has sat without approval for a long time, but it is ready to be merged.

[IanButterworth]

The issue was this: #45 (comment)

So we're ok with releasing 0.4 on the current master? And let's get #61 pushed out quickly after

[mgkuhn]

#61 still needs to fix the default flow-control settings, such that the binary-transparency tests also pass on e.g. Ubuntu Linux (where XON/XOFF is active by default). But feel free to merge #61 into master and I'll then quickly follow up with PRs for that, and perhaps also for restoring the timeout functionality.

[samuelpowell]

Okay, I'll do a release of 0.4, merge #61 and open an issue linking the comment above pending PR and then potentially 0.5

[IanButterworth]

Just beat you to it @samuelpowell. I registered current master as 0.4 801de82#commitcomment-41470735

[samuelpowell]

Cross post - I also asked for registration, both requests link to the same PR on registry so it appears the outcome is okay. I will open issue about #61 now.

[samuelpowell]

0.4 released, hopefully tagbot will tag shortly, will merge #61 to master