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
In order to meet the needs of the Flex Layout community, I am introducing a policy of expedited issue handling. This is needed due to the decreased number of cycles available from the entirely open-source nature of this project's maintainers (aka we are not on the Google team).
Therefore, if you have a documented issue, and have the ability to do so, please provide a Flex Layout test case that shows the issue clearly as broken. If you do so, our guaranteed SLA on the issue is one week (that is to root-cause and at least design a possible solution). All other issues with StackBlitz reproductions will be dealt with in the order of severity and community need.
I hope this provides clarity to our users, and we thank you for your continued interest and support in this project. We'd love to be able to devote more time to this project, but the reality is it's simply not as much a priority of the Google team, and @ThomasBurleson and I only have so much extra time to spare.
Feel free to comment about this process below. If there's another way to expedite issue triage, I'm open to ideas.
The text was updated successfully, but these errors were encountered:
Hello all,
In order to meet the needs of the Flex Layout community, I am introducing a policy of expedited issue handling. This is needed due to the decreased number of cycles available from the entirely open-source nature of this project's maintainers (aka we are not on the Google team).
Therefore, if you have a documented issue, and have the ability to do so, please provide a Flex Layout test case that shows the issue clearly as broken. If you do so, our guaranteed SLA on the issue is one week (that is to root-cause and at least design a possible solution). All other issues with StackBlitz reproductions will be dealt with in the order of severity and community need.
I hope this provides clarity to our users, and we thank you for your continued interest and support in this project. We'd love to be able to devote more time to this project, but the reality is it's simply not as much a priority of the Google team, and @ThomasBurleson and I only have so much extra time to spare.
Feel free to comment about this process below. If there's another way to expedite issue triage, I'm open to ideas.
The text was updated successfully, but these errors were encountered: