CHIRP

Dan Smith wrote in #note-1:

You can see changes from day to day here:

https://chirp.danplanet.com/projects/chirp/activity

That is where we are typing this, no? How do we pull out actual changes amid all the other discussion?

Every day there are changes, there's a build the following day with those changes, so they will map 1:1.
Understood.

Further, each day that a build is generated an email is sent to the mailing list. If you want to be notified, subscribe.
If it is just a notification that there is a build waiting, the software already does that.

We're not going to put the changelog inside chirp or inside the installer because they're usually very small (often only one change per build). Because there are sometimes builds every day for days on end, people are installing them when they are relevant and not installing them when they're not.
I've been installing them every time I open it and it tells me there is a pending update. This is why I wonder what has changed.

Thus there is no expectation that a changelog baked into one night of changes will represent the changes since the version the user currently has installed.

PS: There are no new features for legacy, development is frozen, thus there is no point in a "both" selection. It exists in the drop-down so that people can file bugs and note which version they're using and reporting the issue for, but no new development is being done there.

So, where do I put a bug report for the FT-2800? Against the "legacy", which is supposedly mostly working, or against "Next", which works with an asterisk?

Pretty tough to even make a suggestion here. Not fully understanding the brusque attitude here towards a newbie who is just trying to help.

:-/

That is where we are typing this, no? How do we pull out actual changes amid all the other discussion?

No? Choose "changesets" on the right if you only want to see changes to the software:

https://chirp.danplanet.com/projects/chirp/activity?show_changesets=1

So, where do I put a bug report for the FT-2800? Against the "legacy", which is supposedly mostly working, or against "Next", which works with an asterisk?

Pretty tough to even make a suggestion here. Not fully understanding the brusque attitude here towards a newbie who is just trying to help.

I'm honestly not sure where the confusion is. The "brusque attitude" comes from me being frustrated with what seems like you commenting on closed and unrelated bugs and asking to implement something you don't even have the cable for yet (to see that it's implemented, but perhaps needs work per ChirpNextBuild). I'm not trying to make you go away, but I would appreciate if you would slow down a bit, do some reading of the things provided, and do what I've asked with regard to the 2800. I've suggested subscribing to the mailing list for usage questions, and that includes questions about how to report issues, request new models (when that is appropriate), etc, although much of that is covered in the FAQ.

I really don't want to discuss #10605 in this issue, but I'll respond to your comment above. I hope that we can take further discussion to a new bug when you're able to provide an actual report.

The 2800 driver in -next does work fine for editing images, and is the reason it is already "supported" there. However the cloning routines are the untested bit in -next and are the piece likely to not work due to underlying changes in -next. That's the reason for the asterisk on the front page, merely that it is untested. It could totally work, and if it does, I'll mark it as such with your test report.

The rub is that Yaesu radios in general are very finicky, as they really aren't meant to be programmed by the PC. That is why you have to do the insane button dance with them to "clone" to and from the PC. They're sensitive to timing, cabling, OS drivers, and seemingly even the gentleness with which you caress the buttons while doing the dance. So, if it doesn't work in -next, please open a bug and attach the debug log. I will be able to tell if the issues you encounter are related to -next and fix them. However, because that vintage of Yaesu radios are so finicky (and the 2800 is exponentially worse than the average as you can probably tell from the ancient and yet-resolved bugs you've found and commented on) it's also possible that you'll encounter trouble with it that is unrelated to -next and just that radio being so unreliable. So, what I've asked is for you to please confirm with -legacy as a check, as it at least has worked for some people at some time in -legacy. It has yet to be even tried in -next. If the radio doesn't work with -next for reasons not related to -next itself, and you also can't make -legacy work, then there's no point in me trying to fix something more detailed. I have purged nearly all my Yaesu radios (along with my patience for them) and I definitely don't have a 2800, so if there's something very detailed and unrelated to -next, I won't be able to help. However, if it just requires some conversion for next, I'll be glad to get it marked off the list with your help.

So, to re-re-summarize in flowchart form:

1. Please try the radio with -next. There is really no point in filing a bug or requesting that it be "added" without seeing if it works or not.
2. If it works, great, please open a report to tell me and we're done. If it does not work:
3. Test it in -legacy to see if your cable, radio, etc works in the last-known-working version
4. Open a bug report for the 2800, against -next, attach your debug log and tell me the result of item 3
5. If the log contains next-related errors, I'll try to fix them and ask you to re-test to see if it works
6. If there are no such issues from item 5 (or we resolve them) and it still doesn't work, I'll have to punt until a developer with a radio and the patience for a Yaesu can resolve it further

If you don't want to test -legacy we can cut out 3 and 6. I was trying to save some time by asking you to cross-check your results with -legacy upfront, but it sounds like I should have waited until we got to 4 and then directed you to test with legacy for a data point. My apologies for confusing you.

I've spent a good amount of time in my evening typing this up again, even though I would normally tell people to go to the mailing list for this sort of thing (which, as you note I already tried). I hope this clears it up, that you get your cable, and are able to help get the 2800 crossed off the list. If you still feel confused, please take this to the mailing list and maybe the crowd-sourced suggestions will resonate with you better than mine.

Dan Smith wrote in #note-4:

That is where we are typing this, no? How do we pull out actual changes amid all the other discussion?

No? Choose "changesets" on the right if you only want to see changes to the software:

https://chirp.danplanet.com/projects/chirp/activity?show_changesets=1

It took me a while, but I found that. It would be nice if it told you which version (I guess by date) those changes go into.

Thank you.