What versions of React Native should be supported?

[brentvatne]

• react-navigation/react-navigation#3690 -- 0.42 doesn't have some methods that we expect to exist.
• React Native 0.54 uses 16.3-alpha, which causes warnings.

Should there be some clear rules on what versions we support so users know what to expect? What should those rules be?

[dantman]

Is there a way we can automatically test old versions of RN one by one until we hit the version that doesn't work, then just declare that as the supported version of RN for that release of React Navigation. Then users know they have to update.

And whenever someone makes a PR that happens to break an old version of RN we stick to a policy of "we'll accept the commit as long as it works in the last 3 (or maybe just 2) versions of React Native".

So we'll support RN as far back as it "just works", but as soon as anyone adds code that uses a newer API, we just update our minimum to match.

[ericvicenti]

That’s a cool idea @dantman! But I’m concerned that there will also be slight issues with older versions that also break compatibility..

…

On Fri, Mar 9, 2018 at 12:42 PM Daniel Friesen ***@***.***> wrote: Is there a way we can automatically test old versions of RN one by one until we hit the version that doesn't work, then just declare that as the supported version of RN for that release of React Navigation. Then users know they have to update. And whenever someone makes a PR that happens to break an old version of RN we stick to a policy of "we'll accept the commit as long as it works in the last 3 (or maybe just 2) versions of React Native". So we'll support RN as far back as it "just works", but as soon as anyone adds code that uses a newer API, we just update our minimum to match. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#30 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABajTfMixUV0PTV4XPKBVDf04YVSR15vks5tcukugaJpZM4Skw3Y> .