[chirp_devel] Plans to get the users involved

[Matthew Poletiek]

Great idea. Looking forward to seeing chirp back in Gentoo's portage.

On Sat, Dec 17, 2022, 11:08 Dan Smith via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> > I couldn't agree more. Now that we're gaining real momentum on py3 and
> reaching critical mass, it's time to focus all our energy on moving
> forward, and let go of the past as rapidly as we can. Being clear about py2
> being in strict maintenance mode will be essential. It will also be crucial
> to jump on any issues that come up with installation of py3 builds, on any
> platform, so that we can make the transition process as painless as
> possible for as many users as possible.
>
>
> Yeah, I'm definitely going to need help with this. I tend to ignore issues
> for radios I don't have, but in a lot of cases, a debug log is enough to
> spot an issue. Especially if it's a leftover ord(str) or similar
> py3-related thing, most people should be able to spot and fix that. With
> the load-module thing, it's also easy to let someone test a fix (assuming
> it's in a driver) before we put it in.
>
> > I think, perhaps just prior to the announcement to chirp-users, or
> perhaps sooner, it might be helpful to add the bug lists from "list of
> requested features" and "list of bugs" in the first document to the list of
> "Custom queries" in the issue tracker (i.e. the right-hand column), to make
> it as easy as possible to find these. It might help reduce duplication as
> people start to use the new builds.
>
> Yeah, I have these saved as personal queries but can make them public when
> the time comes.
>
> In thinking about this, I'm wondering if anyone has a better idea for the
> stream naming. My thought was that in a year, we want to continue having
> daily builds, but be based on the new stuff, and we need to refer to the
> old frozen thing by a name. I don't want to just yank the carpet and start
> calling the new thing daily right away. So, the "daily becomes legacy, next
> becomes daily" dance is what I was thinking. But if anyone has a better
> idea, we should consider it.
>
> Also, I didn't mention it before, but I think that in January, I will
> branch current 'master' as 'legacy' and merge 'py3' into 'master' going
> forward so the default github branch is the new stuff. I'll be sure to make
> noise about that here when it happens.
>
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20221217/a4c0ad7c/attachment-0001.html