-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Description
Board
ALL
Device Description
Not relevant
Hardware Configuration
Not relevant
Version
v3.0.1
IDE Name
Arduino IDE
Operating System
ALL
Flash frequency
not relevant
PSRAM enabled
yes
Upload speed
not relevant
Description
As stated in #8796 you want new issue instead of buinding on the existing. Here you go.
Users have made you aware of the incompatibilities of the 3.0.x version a long time ago. For example here:
#8780
With your rollout of the 3.0.0 as an AUTOMATIC upgrade from 2.0.x you did cause a lot of extra work as a lot of code does not compile any more and then the user complains to the project which is only using your API and not to you who are responsible for the change. That is a major pain. You did issue the rollout in spite of the incompatibility. The 3.0.0 HAL is so different it could as well been another CPU architecture.
This above issue from 2023 shows you were very well aware that the 3.0.0 upgrade was a BREAKING change and nevertheless you did roll it out as an automatic upgrade.
It would have given the world much less grief if you would have created a new package (say esp32:idf5) instead of pretending that esp32:esp32@3.0.x
is an upgrade to esp32:esp32@2.0.x
, a fact that you very well were aware of.
To be clear:
I am NOT complaining about the ESP-IDF API that you do have no control of (as mentioned in #8780)
I am complaining that you have rolled this out as an AUTOMATIC upgrade in spite that as you have admitted you have NO CONTROL OF THE INCOMPATIBILITIES and you were WELL AWARE ABOUT IT.
I would not like want to treat the users of the projetcs where I feel responsible in this way.
Sketch
Any sketch using RMT or Timer or LEDC....
Debug Message
Well, it does not even compile.
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
- I confirm I have checked existing issues, online documentation and Troubleshooting guide.