[chirp_devel] Plans to get the users involved

[Jim Unroe]

> I like straight edges, right angles, and easy-to-remember dates. So, I'm thinking that first thing in January would be a good time to send out announcements to the users, looking to expand the testing to a wider audience. I think an initial blast to the chirp_users list would be good, see how that goes, and then start offering both on the download page.
>
> I also think the plan should be to effectively freeze the py2 branch for anything other than bug fixes at that point, and expect all new drivers to be against the py3 branch only. I feel like we've got some inertia now and we had better capitalize on it. At one point in the past I tried to say "new stuff has to work in py3" but I don't think we were close enough to really make that work (sorry Rick!). But now I think we've got builds, they're clearly usable, and saying that new radios will only be available in the new builds is actually reasonable.
>
> If anyone feels this is premature or not the best plan, speak up here and we can discuss. Actually, please speak up regardless, even if it's "yes, seems reasonable" or "friggin finally". There will be some bumps for sure, but I think if people can continue using the legacy builds for radios that don't yet work on the new stuff, we should be okay.

This sounds like a reasonable plan to me. I will support it.

Jim KC9HI