Skip to content

Merge 0.9 into master#2067

Closed
paf31 wants to merge 11 commits intomasterfrom
0.9
Closed

Merge 0.9 into master#2067
paf31 wants to merge 11 commits intomasterfrom
0.9

Conversation

@paf31
Copy link
Copy Markdown
Contributor

@paf31 paf31 commented Apr 30, 2016

This branch will be used to collect changes for 0.9, just in case we need to make a 0.8.6 in the meantime.

Alternatively, we can choose to merge some open PRs into master instead, and if we get enough before 0.9, make a 0.8.6 release.

@garyb Is your library changes PR ready to merge? I wasn't sure, but I can do the merge if it is (you might want to squash commits first though).

DavidLindbom and others added 8 commits March 21, 2016 17:36
@LiamGoodacre LiamGoodacre mentioned this pull request May 1, 2016
garyb and others added 3 commits May 1, 2016 22:45
* Update for names in new prelude
* Disable psci tests that rely on re-exports
* Use bower rather than git submodule for support dependencies
* Expose missing type declaration suggestion

* Tighten span for type wildcard warnings
@garyb
Copy link
Copy Markdown
Member

garyb commented May 1, 2016

Perhaps we should close this for now to prevent the Travis build queue filling up with changes when things get merged?

@paf31 paf31 closed this May 1, 2016
@paf31
Copy link
Copy Markdown
Contributor Author

paf31 commented May 1, 2016

Yeah, good point 😄

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.

5 participants