Skip to content

[0.51] Commits to cherry-pick into stable release #16614

Closed

Description

@grabbou

The thread containing issues that are blocking 0.51 release and need to be addressed.

Before posting your comment, please read the below quote by @ide:

Please keep this list to critical bug fixes that are new in 0.51 and ideally have been merged into master -- post commit hashes rather than issue/PR numbers unless the issue/PR in question targets a problem specific to 0.51. The intent of these cherry-pick threads is not to solicit features but to fix things that make 0.51 substantially more launch-blocked than 0.50. This is an example of an appropriate PR, which fixes the Podspec so 0.51 compiles: #16664

Activity

  1. svbutko commented on Oct 31, 2017

    @svbutko
    Contributor

    Would be great to have these: #16429, #14720, and especially #16456

  2. robblovell commented on Nov 3, 2017

    @robblovell

    Would be amazing if this was addressed: #10999

  3. ide commented on Nov 3, 2017

    @ide
    Contributor

    Please keep this list to critical bug fixes that are new in 0.51 and ideally have been merged into master -- post commit hashes rather than issue/PR numbers unless the issue/PR in question targets a problem specific to 0.51. The intent of these cherry-pick threads is not to solicit features but to fix things that make 0.51 substantially more launch-blocked than 0.50.

    This is an example of an appropriate PR, which fixes the Podspec so 0.51 compiles: #16664


    Cherry-picked 2a24b7b (Podspec fix) and a follow-up commit into 0.51-stable.

  4. grabbou commented on Nov 4, 2017

    @grabbou
    ContributorAuthor
  5. dickie81 commented on Nov 6, 2017

    @dickie81

    Please can we have 3f1b021
    It addresses Android inconsistencies when interpreting line height described here: #10712

    Many thanks.

  6. grabbou commented on Nov 7, 2017

    @grabbou
    ContributorAuthor

    Right now 0.51.0-rc.0 is not out yet on npm due to issues with CircleCI. Until that happens, please hold with posting commits to cherry-pick - all in all you don't know what is broken and needs a fix and what's not :)

  7. deleted a comment from yaronlevi on Nov 7, 2017
  8. deleted a comment from tanthanh289 on Nov 7, 2017
  9. deleted a comment from tanthanh289 on Nov 7, 2017
  10. deleted a comment from spearmootz on Nov 7, 2017
  11. grabbou commented on Nov 7, 2017

    @grabbou
    ContributorAuthor

    @svbutko and @robblovell, PRs that you have linked are not yet merged into master and I don't see how they could be critical to this release.

    I've deleted other, not related comments in this thread. Please keep it to the point and post comments as per @ide guidelines.

  12. deleted a comment from dbyilmaz on Nov 17, 2017
  13. charpeni commented on Nov 27, 2017

    @charpeni
    Contributor
  14. grabbou commented on Nov 27, 2017

    @grabbou
    ContributorAuthor

    @charpeni I see that the commit you have nominated is more a minor feature rather than a hotfix. Would you mind providing a bit more context as to why you would like this one to be cherry-picked?

  15. charpeni commented on Nov 27, 2017

    @charpeni
    Contributor

    ee3532b - Without this fix, our logs in iOS are spamed with this warning:

    Module RCTTVNavigationEventEmitter requires main queue setup since it overrides init but doesn't implement requiresMainQueueSetup. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.

    b9e7006 - Nit picking in the previous warning message, can be omitted.

  16. 6 remaining items

  17. patw0929 commented on Dec 4, 2017

    @patw0929
    Contributor

    It seems that 0.51.0-rc.3 is not released in NPM yet, please help 😄

  18. chrusart commented on Dec 4, 2017

    @chrusart
    Contributor

    @grabbou , this pipeline info brings not much if we can see that it stuck on hold for few days ;)
    And you told us it's gonna be released 3 days ago :)
    So, why still on hold?

    I see there is 0.51.0-rc.2 on npm, ok, it's all about 51-RC for now.

  19. grabbou commented on Dec 4, 2017

    @grabbou
    ContributorAuthor
  20. grabbou commented on Dec 4, 2017

    @grabbou
    ContributorAuthor
  21. jslok commented on Dec 5, 2017

    @jslok

    @grabbou is 0.51.0 supposed to be available in npm right now? I only see 0.50.4 still. It shows success in your circleci link but I'm not exactly sure what this entails. Sorry if I'm jumping the gun and thanks for your time.

  22. chrusart commented on Dec 5, 2017

    @chrusart
    Contributor

    @jslok it's 0.51.0-rc.3 build for now.

    It's on npm.

  23. richardgirges commented on Dec 5, 2017

    @richardgirges

    0.51.0-rc.3 seems like the best option for now since stable release isn't up yet. Wondering where the best place is to look at a change log @grabbou ? Thanks!

  24. grabbou commented on Dec 6, 2017

    @grabbou
    ContributorAuthor
  25. Noitidart commented on Dec 6, 2017

    @Noitidart

    @grabbou in stable, flowconfig is set for version 0.57.0 there is no such version. Only 0.57.1 or .2 or .3. when I do npm i flow-bin@0.57.0 --save-dev it says no such package.

  26. tiagoalves commented on Dec 7, 2017

    @tiagoalves

    I'm late to this but if my analysis is correct, #17030 seems to be a serious regression that should be fixed in v0.51.

  27. grabbou commented on Dec 7, 2017

    @grabbou
    ContributorAuthor

    Subscribed and will be awaiting status. For now, going to close this one as no cherry-picks to stable anymore except the bug fixes that we will track separately.

  28. grabbou commented on Dec 7, 2017

    @grabbou
    ContributorAuthor

    Going to roll out 0.52.0-rc.0 in the meantime.

  29. locked as resolved and limited conversation to collaborators on Dec 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions