obfsproxy's codebase is quite stable lately, and I think its time to take a step into the deployment phase, by tagging an obfsproxy release.
After #3729 (closed) gets in, I suspect that no other "big features" will get merged in the short-term future , and it looks like a good moment to strike with our tag. Specifically, I think we should tag after #3729 (closed), #3726 (closed) and #4920 (closed) get merged (and #4743 (closed) resolved).
After tagging, we can announce the release to tor-talk along with some documentation, ask people to set up obfsproxy/obfs2 on their bridges, and ask them to send us their bridge credentials. This way we will have some obfs2'ed bridges ready for when the "Pluggable Transport Bundle" gets released.
After tagging, we can also talk to Linux distributions and start looking into obfsproxy packaging. I know that blueness, the Tor maintainer of Gentoo was interested in packaging obfsproxy, but he was afraid that it was too beta-ish at the moment. This obfsproxy release will still be beta-ish, but at least he will have a specific milestone in the codebase that he can base his packages on (and maybe the packages can be marked as 'unstable', since I think there is such a concept in Gentoo's portage.)
Nick, what do you think?
PS: Is 'beta' the correct term for this release? I would go with 'alpha', 'gamma', '0.01' or anything really...
: At least till #4685 (moved).