v0.11.0

[DaAwesomeP]

Release v0.11.0

Notes for building: 

• Before testing on each system remember to update (apt, ports etc.)
• From within the ola directory, you can get the compiler version with:
• Make sure you run ./configure --enable-rdm-tests --enable-e133
• Make sure you have all the dependencies installed (libusb-dev, libftdi-dev, liblo etc.) |  

Maintainers should be able to edit/check things off. If you check something off, please add your @ at the end of the line.

• Create a new issue for the release version - @DaAwesomeP done
• Test on as many platform / arch / compiler combinations as you can
• Make sure you have automake >= 1.15
• Check for any new Debian bugs
• Pull in the latest PID data - @peternewman is currently refreshing this via Add new PID data from E1.20-2025 rdm-app#321 and Autoupdated manufacturer data rdm-app#324 but very happy if someone else wants to try the import process to get familiar with it?
• Check a few copyright dates and update if necessary - @peternewman these are in something I've committed somewhere...
• Check the NEWS file one last time - @peternewman is currently working on updating this
• Pull in the Debian changes - @DaAwesomeP this is good for now once we merge Update Debian Package Services and Config Directory #1855. There are some minor man pages things we can table for now and the rest are compiler related things to fix in v0.12.0
• Increase the version number & commit <- this is the release
• Tag the release commit with the version number
• Run make dist to produce a tarball
• Upload the tarball
• git push --tags
• Branch the release off
• Protect the new branch including status checks on GitHub
• Close the existing milestone
• Create a new milestone for the next point release
• Post on the mailing lists (bcc the other lists), G+, Twitter, FB etc.
  • open-lighting-announce@googlegroups.com
  • open-lighting@googlegroups.com
  • rdm-testing@googlegroups.com
• Email people to make debs
• Possibly update the RasPi image
• Update Macports
• Make a new doxygen snapshot
• Update NEWS with a placeholder for the next release

cc @aroffringa @peternewman @nomis52
Result of #2035

[peternewman]

I've started on a branch which has everything good without the C++11 breaking couple of commits that got dragged in, which is currently here, unless someone has a neater way to do it (having tried doing reverts before it just got very messy/confusing, hence an alternative approach):
https://github.com/peternewman/ola/tree/0.11.0-pre-release