The beta cycle for the previous major release in Q4 2018 was pretty informal–I just put it out there, and whoever picked it up could install it. But as a result, I felt like I wasn’t getting enough feedback, and there were too many hiccups post-release that could have been caught earlier.
So, for this major release cycle (Reactor 3.0), I’m going to do it as a closed beta available only to those who register with me prior to participate, so I can know who is using it, stay in touch, and better understand what areas you are most focused on, and thus identify any potential holes in coverage.
If you would like to participate in the Reactor 3.x Beta, please email me at [tt]reactor-beta <[at]> toggledbits <[dot]> com[/tt]. Please include your Vera community username, so I can connect the dots.
But before you email me, please read the following, so you understand some important details:
[ul][li]Reactor 3.x configurations are not backward compatible, and there is no way to make them backward compatible (I’m introducing new features and structure for conditions that have no analog in prior versions). A Reactor backup before first installing the beta will be necessary to capture your 2.x configuration should you want to revert to the earlier version (3.x actually does this automatically, but doing it yourself for good measure, and saving the backup off-Vera on a local drive, is highly recommended); a full Vera backup in addition is also a Very Good Idea.[/li]
[li]If you are planning on participating in the beta using the one and only Vera/openLuup system you may have, you are assuming the risk of encountering significant bugs in your own home’s production environment. That’s up to you. I will be working diligently and quickly to chase any and all reported bugs and get them resolved as fast as possible, but that still may mean hours or more. I will not be responsible for ire or ridicule by your significant other if you decide to make your entire household a participant. 
[/li]
[li]You should be familiar with the task of pulling Vera log files to your local computer and uploading or emailing all or part.[/li]
[li]To help me stay organized, I will be taking bug reports and issue/idea discussions only as Github issues, so you will need a Github account (free) to participate. This will also help keep the forum threads clear of issues in interim versions that most people will never see.[/li]
[li]Most importantly is, if you choose to participate, that you actually participate. I can test this thing to death, but as anyone who has ever tested software knows, as soon as you put something in some else’s hands, even the most trivial difference in the way they approach it can make all the difference in uncovering faults. I need your full participation to help ensure the best release possible for everyone in the community.[/li][/ul]
Timing-wise, I do not plan on starting the beta until mid-March, and I’d like to see it running on 7.0.29 (their recently-announced firmware upgrade) before release if possible. So my plan of record at this moment is to start this Reactor beta on 3/20, with a target end of 5/10 and release 5/13. If stars and planets align and the release date can be pulled in, I will.