Final Pull Request for FGDS 2015 Updates

[skathan]

Updated text, navigation, and figures

[AlJohri]

@skathan @SpyderRivera @WellingtonPalma

I didn't realize the Field Guide was still being updated after 2013. Would you be able to summarize the changes made in the 2015 edition?

Perhaps include a CHANGELOG in the README?

[skathan]

A lot of the changes are cosmetic: word choices, date updates, error corrections, and new quotes from thought leaders. Alongside them are more substantive changes that include new sections, new data spotlights, and additional techniques. If there's a place I should encode this within the github, please advise.

On Wed, Apr 20, 2016 at 9:58 AM, Al Johri notifications@github.com wrote:

@skathan https://github.com/skathan @SpyderRivera https://github.com/SpyderRivera @WellingtonPalma https://github.com/WellingtonPalma

I didn't realize the Field Guide was still being updated after 2013. Would you be able to summarize the changes made in the 2015 edition?

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/booz-allen-hamilton/The-Field-Guide-to-Data-Science/pull/9#issuecomment-212436499

[AlJohri]

@skathan I don't there's a defacto way to do so. I think in git its usually just done in the form of a description on each commit message. But ain't nobody got time for that.

• One idea is to create a CHANGELOG.md file in the root repository similar to README.md or CONTRIBUTING.md which just lists the major changes for each iteration of the Field Guide.
• Or you can just include something at the bottom of your README.md that list the general changes between the major versions.
• You can also use releases in Github to tag this commit as the final iteration of the 2015 field guide. Would definitely recommend creating a release.

Hope this helps!