Skip to content

[157] Updates for 0.4.0 release - #179

Merged
jkbradley merged 1 commit into
graphframes:masterfrom
jkbradley:branch-0.4.0-rc1
Mar 27, 2017
Merged

[157] Updates for 0.4.0 release#179
jkbradley merged 1 commit into
graphframes:masterfrom
jkbradley:branch-0.4.0-rc1

Conversation

@jkbradley

Copy link
Copy Markdown
Member

Minor updates to docs

@jkbradley

Copy link
Copy Markdown
Member Author

CC @thunterdb @felixcheung Did I miss anything?

Tests ran locally for (spark 2.0, 2.1) x (scala 2.10, 2.11)
I'm also testing the locally published packages.

@jkbradley jkbradley changed the title Updates for 0.4.0 release [157] Updates for 0.4.0 release Mar 27, 2017
@codecov-io

codecov-io commented Mar 27, 2017

Copy link
Copy Markdown

Codecov Report

Merging #179 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #179   +/-   ##
=======================================
  Coverage   88.14%   88.14%           
=======================================
  Files          17       17           
  Lines         717      717           
  Branches       56       56           
=======================================
  Hits          632      632           
  Misses         85       85

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5cfc027...749028e. Read the comment docs.

@jkbradley

Copy link
Copy Markdown
Member Author

Got a LGTM from @thunterdb offline. Merging now.

@jkbradley
jkbradley merged commit e56bbdc into graphframes:master Mar 27, 2017
@jkbradley
jkbradley deleted the branch-0.4.0-rc1 branch March 27, 2017 22:39
@thunterdb

Copy link
Copy Markdown
Contributor

LGTM

@felixcheung

Copy link
Copy Markdown
Member

@jkbradley

Copy link
Copy Markdown
Member Author

So I did update those when building the project, but I didn't want to make the master branch a non-snapshot. Really, we should start cutting actual release branches, rather than just using tags. Let's do that for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants