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
I'd suggest closing all 0.8 and 0.9 issues, with a friendly note asking people to reopen if it's still an issue under the 0.10 branch (or submit a PR with passing tests against the older branch).
A good deal of the issues are already labeled, so gardening should be fairly easy 🌷 🌳.
The text was updated successfully, but these errors were encountered:
I'd suggest first making sure that 0.10 can actually replace 0.8 and 0.9. I think at least one of the sideloading pullrequests should be completed and merged before 0.8 and 0.9 can be phased out like this.
We have iced the 0.8.x and 0.9.x support for now, but we also know that upgrade from older version might be a little tricky, so we are aiming to have a section on our new docs to help ppl into upgrading their apps.
Anyway, I also feels there is a lot of older issues that might not even suit the older version, I think after 0.10.x release we need some sorte of clean up as suggested here. But right now we would not be able to handle ppl reopening issues and asking about updates on older versions.
I'd suggest closing all 0.8 and 0.9 issues, with a friendly note asking people to reopen if it's still an issue under the 0.10 branch (or submit a PR with passing tests against the older branch).
A good deal of the issues are already labeled, so gardening should be fairly easy 🌷 🌳.
The text was updated successfully, but these errors were encountered: