Preparation for 2.5M2

[marcel_erkel]

I hope you read those threads too

@Kai

So the first step for which we use our new ability is to provide milestone releases from now on. The plan is to have roughly one milestone release per month. They are meant to be a pretty good compromise between the nightly snapshots and the official releases. I know that many of you are using snapshots even for their production system (me included) and you continuously run the risk that you catch a snapshot that completely breaks your system. Waiting for a new release is no option either, if you want to use new features that only recently made it into the code base. With the new milestone builds, we will make sure that those builds work in general and that they should not have any (known) critical issues. They should therefore be a nice option if you want to be on the latest&greatest, but want to avoid the risks that are associated with snapshots builds.

(Bold by me)

Yes, the idea is that milestone builds are released roughly each month and we all know why that process has stalled.
More importantly though, they should not have any (known) critical issues.

@5iver

I see all of these as critical…

1. This one will cause issues for anyone using more than one serial device.
2. Definitely a blocker, but there may be a workaround.
3. A migration script needs to be built.
5. hueemulation is currently non-functional, and IMO, this should be a blocker due to the number of people using this binding.
7. Possibly related to 2.
8. Possibly related to 2.
9. allplay and bluetooth could have enough usage to call this a blocker
10. Blocker, but there may be a workaround.

(Strike-through by me; these issues have been fixed)

I’m sorry that I value the opinion of those who contribute to the code higher than the opinion of the ones that don’t.

Patience is a virtue.