Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ev3dev-stretch #52

Open
dlech opened this issue Sep 17, 2017 · 8 comments
Open

ev3dev-stretch #52

dlech opened this issue Sep 17, 2017 · 8 comments

Comments

@dlech
Copy link
Contributor

dlech commented Sep 17, 2017

How do you plan on handling breaking driver changes in ev3dev-stretch? For example, port names and LED names have changed.

@kortschak
Copy link
Member

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?

@dlech
Copy link
Contributor Author

dlech commented Sep 17, 2017

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.

@kortschak
Copy link
Member

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.

@kortschak
Copy link
Member

BTW Can you point to new naming conventions?

@dlech
Copy link
Contributor Author

dlech commented Sep 17, 2017

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.

@kortschak
Copy link
Member

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.

@kortschak
Copy link
Member

kortschak commented Oct 22, 2017

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?

@dlech
Copy link
Contributor Author

dlech commented Oct 22, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants