Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CHANGELOG.md for 0.7.0 #97

Closed
wants to merge 3 commits into from
Closed

Update CHANGELOG.md for 0.7.0 #97

wants to merge 3 commits into from

Conversation

yungsters
Copy link
Contributor

This is just a placeholder with a list of changes since 0.6.0. We can update / replace it when 0.7.0 is actually published.

cc @zpao

@ide
Copy link

ide commented Jan 21, 2016

@zpao what's your thinking around the timeline for 0.7.0? @skevy's recent fbjs diffs fix some RN issues people are having (facebook/react-native#5467 is one of the top bugs -- skevy tells me his fbjs changes + some RN packager changes should resolve it) and allow Relay to work with RN. So the earlier we get a new fbjs release the sooner RN can ship with Relay compat.

@zpao
Copy link
Member

zpao commented Jan 21, 2016

I meant to followup on this sooner, sorry.

So I guess the question is, how will the cascading of fbjs versions work? I know we updated fbemitter explicitly to get all the RN deps using 0.6. But we aren't going to upgrade React for every fbjs release so that's not a maintainable approach.

@ide
Copy link

ide commented Jan 21, 2016

Part of the fbjs and packager changes are to ignore some of the providesModule declarations so I think it'll be fine if there are multiple copies of fbjs. It might be necessary for react and fbemitter to upgrade to 0.7 one time (I don't think so though).

@sophiebits
Copy link
Contributor

Yeah, starting with RN 0.19 it's fine to have more than one fbjs.

@martinbigio
Copy link

@zpao, @spicyj we're blocked to land facebook/react-native#5084 up until a new release of fbjs is done (unless we depend on a commit, which I guess is not ideal, right?). There's no rush, just wanted to get an idea when you were planning to release the next version :)

@skevy
Copy link
Contributor

skevy commented Jan 25, 2016

Also, it's in the changelog, but #100 should be pulled in as well.

@ide
Copy link

ide commented Jan 25, 2016

Depending on the commit would actually be a good way to move forward but fbjs has some prepublishing scripts so we need to grab it from npm.

@tlvenn
Copy link

tlvenn commented Jan 27, 2016

@zpao Any update on the timeline ? Sorry to sound impatient but I am kinda excited to see the day where Relay and RN just work together. Thanks in advance.

@zpao
Copy link
Member

zpao commented Jan 27, 2016

Gonna take a closer look at things today.

@zpao
Copy link
Member

zpao commented Jan 27, 2016

Pushed 8a84822 which mostly overlaps with this (but doesn't give it the version number). I think I'll merge #105 and then call that 0.7.

@zpao zpao closed this Jan 27, 2016
@skevy
Copy link
Contributor

skevy commented Jan 27, 2016

Thanks @zpao!

@zpao zpao deleted the yungsters-0.7.0 branch April 5, 2016 03:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants