Manuel

> it makes us unable to use new features for up to 1 year Can you give an example of a new feature that is not available because we still...

> One of the new features of Dart 3 is [Multiple returns](https://dart.dev/language/records#multiple-returns), which allows us to have multiple output values in the function The question is whether that impedes Parse...

> it also prevents developers from using other packages that do not support versions below 3 ! Are you talking about app developers, and if yes, why would that be?...

> And currently, most of the famous packages no longer support versions below 3. If you check the [pub.dev](https://pub.dev/) site, you will understand this! Let's do a quick analysis. There...

In time terms: - Dart 2.18, released Aug 2022 -> time passed since release: 1 year + 1 month - Dart 2.12, released Mar 2021 -> time passed since release:...

Would you want to do the honors? 🙂

Yes, from the CI you'd remove Dart 2.18. And we should add Dart 3.1 compatibility. You could do this in 1 PR. The PR would be a `feat` PR because...

> What would happen if we were to bump major versions of our SDK when backward compatibility breaks and keep up with the latest dependencies? How would such a policy...

@mbfakourii I've re-opened the issue and pinned it. Reason being that I'd like to review the policy since we've introduced it about a year ago. We keep getting issue reports...

A support policy is simply making sure we have a consistent approach and don't need to initiate a discussion every time we need to make a choice. We can define...