You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.
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.
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>
.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Should there be some clear rules on what versions we support so users know what to expect? What should those rules be?
The text was updated successfully, but these errors were encountered: