Corrected API-Calls to Versioning

[sreuterle]

Versioning methods are called directly on widget instead through widget.paper_trail

[jaredbeck]

Thanks Sven, but these changes would be incorrect. For example, widget.live? is actually deprecated in favor of widget.paper_trail.live?. See #719

[sreuterle]

Oh, sorry for that. I've version 5.0.1 installed and there seems to be no widget.paper_trail (for corresponding object for widget). I try to update to latest version. Thanks you :)

[jaredbeck]

Oh, sorry for that. I've version 5.0.1 installed and there seems to be no widget.paper_trail (for corresponding object for widget). I try to update to latest version. Thanks you :)

widget.paper_trail has not been released yet. You are reading the documentation for the master branch. I'll see if I can clarify that a bit better at the top of the readme.

[sreuterle]

Maybe it would be better to make a release branch until release so that master corresponds to released version on every time. That's how we handled branches in our company.
Then, of course, the readme would correspond to the released version, too.

[jaredbeck]

Maybe it would be better to make a release branch until release so that master corresponds to released version on every time.

Thanks for the suggestion, but there is a strong convention in the ruby OSS community that the master branch represents the very latest work, and tags are used for releases. Following the convention has value.

[sreuterle]

Didn't knew that. Thanks for clarifying!