Skip to content

Conversation

@ararslan
Copy link
Member

This shuffles a few support tiers:

  • 32-bit Windows shifts from tier 1 to tier 2 support. This will allow to continue working on releases even if Win32 is being finicky with some tests. (This is the case for v1.4.0, with Win32 intermittently failing the Distributed tests.)

  • AArch64 shifts from tier 2 to tier 1. We have CI that ensures that AArch64 builds and passes tests, and it has been doing so consistently for a while now.

  • ARMv7 shifts from tier 2 to 3. We've had a number of issues on ARMv7, which have made producing release binaries quite tricky due to build failures and other issues.

This shuffles a few support tiers:

* 32-bit Windows shifts from tier 1 to tier 2 support. This will allow
  to continue working on releases even if Win32 is being finicky with
  some tests. (This is the case for v1.4.0, with Win32 intermittently
  failing the Distributed tests.)

* AArch64 shifts from tier 2 to tier 1. We have CI that ensures that
  AArch64 builds and passes tests, and it has been doing so
  consistently for a while now.

* ARMv7 shifts from tier 2 to 3. We've had a number of issues on ARMv7,
  which have made producing release binaries quite tricky due to build
  failures and other issues.
@ararslan ararslan changed the title Support tier shuffle: Win32, ARMv7 -= 1, AArch64 += 1 RFC: Support tier shuffle: Win32, ARMv7 -= 1, AArch64 += 1 Mar 17, 2020
@KristofferC KristofferC merged commit 55ff318 into master Mar 19, 2020
@KristofferC KristofferC deleted the aa/tiers branch March 19, 2020 11:34
@ararslan
Copy link
Member Author

Would this be worth a Discourse post to announce the changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants