Open dlech opened 6 years ago
My approach in the past has been to support the most recent needed ev3dev version. This could be extended to only support the current major version, but place a git tag at the last jessie-supporting commit so people can manually check that out. Do you have any suggestions?
That sounds reasonable. I'll probably start advertising ev3dev-stretch as "beta" soon. Personally, I don't use jessie anymore at all at this point. So, I'm just wondering how to test #50 without having to go back to jessie. My plan is to just update my local copy of https://github.com/ev3go/ev3.
The other alternative is to guard the name constants with build tags, but that adds complexity to support and I probably won't do that.
BTW Can you point to new naming conventions?
https://github.com/ev3dev/ev3dev-kpkg/blob/ev3dev-stretch/ev3dev-ev3/changelog
basically, EV3 ports have a prefix of ev3-ports:
now and LEDs are something like led0:green:brick-status
.
I have decided the best way to do this is to make a persistent jessie branch from the point where the changes occur. This allows a period of bug maintenance after the fork for people who stay with jessie.
I have a couple of branches ready for PRs for the stretch transition. I need to look at the BrickPi to see what changes need to happen there (just LEDs from the looks of it).
https://github.com/ev3go/ev3dev/tree/ev3dev-stretch https://github.com/ev3go/ev3/tree/ev3dev-stretch https://github.com/ev3go/brickpi/tree/ev3dev-stretch
Feel free to try them out - I've done minimal on-platform testing at this stage, and will only be able to get to that likely late in the week.
Do you have a time frame for the change over for ev3dev to stretch?
Optimistically, I would like to start advertising stretch as "beta" by the end of the year. We'll see if that actually happens or not.
How do you plan on handling breaking driver changes in ev3dev-stretch? For example, port names and LED names have changed.