Thanks to everyone who voted :pray: . The more I'm...
# library-developmentm
mbonnin
07/21/2022, 8:41 AMThanks to everyone who voted 🙏 . The more I'm thinking about it the more I'm leaning towards the unpopular 2️⃣ solution though..
Reasons are that upgrading a lib to 1.7 forces:
• every consumer project on 1.6
• every native consumer project on 1.7
• every Gradle plugin consumer project to spit out tons of warnings (or maybe crash)
The main advantage is that it allows to use the new 1.7 APIs and features of course but very often the public API of the lib itself is not impacted by this so this is transparent to users.
All in all, feels like upgrading to 1.7 is nice for maintainers but not so nice for consumers. I get that moving the ecosystem forward is healthy and all but feels like giving a couple of months of headstart would help moving all the thing in a more coordinated way. What am I missing?