Prepare for 0.2.1 release

[itziakos]

This PR updates the changelog and readme with information on the upcoming 0.2.1 release

[coveralls]

Coverage remained the same when pulling a7944af on prepare-for-0.2.1-release into 7dd4d84 on master.

[coveralls]

Coverage remained the same when pulling 02954d4 on prepare-for-0.2.1-release into 7dd4d84 on master.

[coveralls]

Coverage remained the same when pulling ca40ee6 on prepare-for-0.2.1-release into 7dd4d84 on master.

[coveralls]

Coverage remained the same when pulling bff8e95 on prepare-for-0.2.1-release into 7dd4d84 on master.

[coveralls]

Coverage remained the same when pulling cea78d8 on prepare-for-0.2.1-release into 7dd4d84 on master.

[pberkes]

Cool! This reduces the risk of being burned by enaml changes.

[itziakos]

Yes, now we run on latest masters, released versions in pypi and old releases.

[pberkes]

👍

[coveralls]

Coverage remained the same when pulling 8d00c50 on prepare-for-0.2.1-release into 7dd4d84 on master.

[coveralls]

Coverage remained the same when pulling 8d00c50 on prepare-for-0.2.1-release into 7dd4d84 on master.

[jwiggins]

We might have found a bug introduced by #55 in a client project. I'm looking into it now and will add details when I know more.

[jwiggins]

Ok. So the problem can be worked around in application code, but the TraitsTracer shouldn't raise an exception under that particular circumstance (a Property trait with no other type information).

[itziakos]

Thanks @jwiggins, I will delay cutting version 0.2.1 until #57 is fixed.

[itziakos]

One more thing @jwiggins, are you already working out of traits-enaml master? Do you need to revert the changes in #55 until #57 is fixed?

[jwiggins]

We are working out of master because we need the fixes provided by #55. Fortunately, we can work around the problem by declaring our property traits correctly.

[itziakos]

It is ok to cut the new release?

[jwiggins]

Go for it!