Add v1.0.0 release to changelog #340
Conversation
|
OK, looks like we have consensus that we want to release this as-is. @ddemidov Is it you who knows how to actually release the thing (and has access to the package repository) 😆? |
That is correct. At least I hope I would be able to remember how to do this. I should really listen to @dlech and create a script for this. I'll release as soon as possible. |
|
Haha, sounds great! Remember to add the release info (i.e., your name) at the bottom of this changelog file. We also need to figure out where else the version number is and update it... |
|
I'll add more commits here as necessary. |
|
I've pushed dc2ffc8 directly to develop/master, so I am closing this. I've also uploaded debian/raspbian packages to the package repo (tested on debian-jessie) and created a new tag. @WasabiFan, would you like to create a release announcement? |
|
@ddemidov will-do., thanks! |
|
🎉 https://github.com/rhempel/ev3dev-lang-python/releases/tag/1.0.0 Feel free to edit as desired. |
I think it's time that we tag a v1.0.0 release. As noted in #339, we have some breaking changes to make for ev3dev-stretch; that seems to be a good occasion to release a major version of the library for ev3dev-jessie and then reconfigure branches and change modes to work on Stretch.
The branch-relative comparison can be found here, or you can look here for a future-proof static comparison. In the changelog I omitted some README and demo changes; I can't recall if those demos are included in the package or not, but I can add those entries if needed.
We have a few features open right now that we might want to land before this release; specifically, #336 and the work for #331 here.