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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release SDK32 #3030

Closed
tsapeta opened this issue Dec 20, 2018 · 31 comments

Comments

@tsapeta
Copy link
Member

commented Dec 20, 2018

SDK32 release plan

Creating new release issue as it seems like the previous one was accidentally deleted by someone 馃槺

@tsapeta

  • Update libs: GestureHandler, Reanimated, Screens #2977
  • Drop SDK25 #2995
  • Update schema on staging
  • Version Android code #3003
  • Review changelog #3006
  • QA Expo Client on Android #3010
  • Publish prerelease packages
  • Publish dev and prod home
  • Tag react-native fork sdk-32.0.0
  • Publish NCL to Apple's account
  • Update expokit-npm-package #3093
  • Push Android Turtle to staging
  • Push Android ExpoKit
  • Add Android apk
  • Release Android in Play Store
  • Promote versions to prod
  • Mark SDK 25 as deprecated on server

@sjchmiela

  • Drop SDK25 #2986
  • cherry pick ListView fix from react-native repo (see discussion below)
  • Version iOS code #2999
  • Prepare changelog #3006
  • QA Expo Client on iOS #3010
  • Generate new mocks and update jest-expo
  • Update versions on staging
  • Submit for Apple review
  • Update ExpoKit on staging
  • Rollout Expo Client build for Simulator
  • Tag iOS ExpoKit
  • Publish packages to npm
  • Push schema to production
  • Release iOS in App Store
  • Update new project templates on staging

@dsokal

  • Release xdl and expo-cli
  • Push iOS Turtle to staging
  • Release iOS Turtle to prod
  • Release Android Turtle to prod
  • Release turtle-cli

@esamelson

  • Publish new docs
  • Publish blog post with release notes
  • Add release notes to docs
  • Update website front page
  • Post on Twitter
  • Publish NCL to @ community account

@tsapeta tsapeta added the in progress label Dec 20, 2018

@tsapeta tsapeta added this to the SDK32 (M34) milestone Dec 20, 2018

@tsapeta tsapeta pinned this issue Dec 20, 2018

@iamkevinwolf

This comment has been minimized.

Copy link

commented Dec 22, 2018

Will this support react hooks?

@jamespacileo

This comment has been minimized.

Copy link

commented Dec 23, 2018

There have been a lot of react-native-web related PRs getting merged, but I don't see any mention of react-native-web support on the milestone release plan.

Are you planning to unofficially release web support as well with this release? Thanks 馃槃

Just wondering, because that would be awesome!

@wassgha

This comment has been minimized.

Copy link

commented Dec 26, 2018

No background location in this release? #2338

@ChronSyn

This comment has been minimized.

Copy link

commented Dec 27, 2018

No background location in this release? #2338

Is there any reason it wouldn't be, considering it was merged?

This issue is a checklist of things to be done to release the expo 'platform' to the next SDK version. It doesn't have anything to do with what is included in the release.

@ide

This comment has been minimized.

Copy link
Member

commented Jan 2, 2019

@kevinwolfcr Hooks are not stable in React itself yet. Once hooks are released in a stable version of React, then RN will later upgrade React. Once RN stabilizes, we then have a path to bring hooks to Expo.

@jamespacileo Web is still a ways out and is pre-experimental. When it is ready, we will announce it with the release notes at that time on blog.expo.io.

@ide

This comment has been minimized.

Copy link
Member

commented Jan 2, 2019

I pushed a branch called sdk-32 (based off of master; feel free to force-push if it needs to point at an older commit) so that new commits to master don't accidentally go out with the release.

@vractal

This comment has been minimized.

Copy link

commented Jan 4, 2019

Hi, im having problems with the expo client since today:
image
Perharps it could be related to this merge?

@tsapeta

This comment has been minimized.

Copy link
Member Author

commented Jan 4, 2019

@vractal Yes, I'm fixing this issue right now. Sorry for the trouble 馃槥 The fix will be out soon.

@vractal

This comment has been minimized.

Copy link

commented Jan 4, 2019

@tsapeta Don't worry, thank you! :)

@Softrabbit-de

This comment has been minimized.

Copy link

commented Jan 4, 2019

Hi, im having problems with the expo client since today:
image
Perharps it could be related to this merge?

Until fix is available a little workaround ;-)
Just update the sdkVersion in app.json
"sdkVersion": "32.0.0",

@tonycoco

This comment has been minimized.

Copy link

commented Jan 4, 2019

Getting errors with Unable to resolve "./Amplitude" from "node_modules/expo/build/Expo.js"

@isaacnass

This comment has been minimized.

Copy link

commented Jan 4, 2019

@tonycoco try resetting your metro cache (shift + R), see if that works

@burtek

This comment has been minimized.

Copy link

commented Jan 4, 2019

When can we expect new docs, release notes and upgrade instructions? 馃槂

@esamelson

This comment has been minimized.

Copy link
Member

commented Jan 4, 2019

we're working on it! :)

@burtek

This comment has been minimized.

Copy link

commented Jan 4, 2019

@esamelson right, thx for quick reply :)

@isaacnass

This comment has been minimized.

Copy link

commented Jan 4, 2019

@tonycoco

This comment has been minimized.

Copy link

commented Jan 4, 2019

@isaacnass works fine now with a reset. Any way to do it from the CLI? Used expo start --reset-cache in the past, but that seems lost now.

@burtek

This comment has been minimized.

Copy link

commented Jan 4, 2019

@isaacnass THX!!! 馃槂

@isaacnass

This comment has been minimized.

Copy link

commented Jan 4, 2019

@tonycoco I believe shift + R while in the CLI will do it. Glad you got it working!

@tonycoco

This comment has been minimized.

Copy link

commented Jan 4, 2019

@isaacnass ahh, I meant shift+r works fine from within the CLI. But, from the command itself, expo, is there a way to force a cache reset?

@danikane

This comment has been minimized.

Copy link
Contributor

commented Jan 4, 2019

expo start -c

@andresmtz98

This comment has been minimized.

Copy link

commented Jan 4, 2019

Hi. Sorry to write here but there is a critical bug for those who use the "expo-print" module on iOS. I did the post a few days ago. I hope you can review it when you have time and see if with this release you can fix it :3

@tonycoco

This comment has been minimized.

Copy link

commented Jan 4, 2019

expo/vector-icons#74 still needs to be merged too

@Chanty-SOK

This comment has been minimized.

Copy link

commented Jan 5, 2019

Don't this issue have the solution yet?

@spyshower

This comment has been minimized.

Copy link

commented Jan 5, 2019

What version of RN does this version ship with?

@zivester

This comment has been minimized.

Copy link

commented Jan 5, 2019

I just got an Android update a couple minutes ago (hasn't worked since yesterdays release) and now instead of Blue Screening for incompatibility it hard crashes. expo@27.0.0 and latest Expo from Play store.

@jaulz

This comment has been minimized.

Copy link
Contributor

commented Jan 6, 2019

@isaacnaas any chance to include this commit facebook/react-native@cd8051c as well?

@ChronSyn

This comment has been minimized.

Copy link

commented Jan 6, 2019

@isaacnaas any chance to include this commit facebook/react-native@cd8051c as well?

The SDK has shipped and the only things still to do appear to documentation. Thus, there's unlikely to be any more cherry-picking for the release, though it may make it into a minor release if the team deem it worthwhile.

@jaulz

This comment has been minimized.

Copy link
Contributor

commented Jan 6, 2019

@ChronSyn okay, thanks for the feedback anyway!

@pbandjs

This comment has been minimized.

Copy link

commented Jan 7, 2019

I just got an Android update a couple minutes ago (hasn't worked since yesterdays release) and now instead of Blue Screening for incompatibility it hard crashes. expo@27.0.0 and latest Expo from Play store.

It hard crashes for me with expo@26.0.0 as well.

@sjchmiela

This comment has been minimized.

Copy link
Contributor

commented Jan 7, 2019

Hey all, thank you for all the consideration and eagerness to try all the new features we've prepared! We really appreciate the enthusiasm! 馃槏

To let us and you work more efficiently, I'll lock this conversation鈥攑lease file, as usual, separate GitHub issues for separate problems. For quick questions I would recommend our Slack community, which has always been really helpful!

Have a nice day! 鈽锔

@expo expo locked as too heated and limited conversation to collaborators Jan 7, 2019

@esamelson esamelson unpinned this issue Jan 7, 2019

@esamelson esamelson closed this Jan 7, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can鈥檛 perform that action at this time.