search

w7sst / MorseRunner

Morse Runner Community Edition
Mozilla Public License 2.0
61 stars 12 forks source link

wrap up Milestone v1.82 - what's left to finish #142

Closed w7sst closed 1 year ago

w7sst commented 1 year ago

@scotthibbs @ct7aup @tekenny @f6fvy @Yagi-Berra

Hi all, I think we are getting close to completing the goals for Milestone v1.82. We talked about fixing a few bugs, adding ARRL DX Contest, and improving introduction materials. I think these items have been completed.

We also had a goal to announce to a larger user community. I was initially thinking of an announcement to the N1MM user group since I had mentioned to them back in early summer that I was working on this. I wanted to announce to them using the same discussion topic when we are ready.

However, we have to be sure we are ready to support this announcement. I'd like to use this Issue as a discussion area to agree we are ready for an larger announcement. I'm hoping to pull back from development activities for the next 6-8 weeks, but will be available for discussions.

So let's start a discussion below (in the comments) and update the following TASK list as needed to work out the remaining details for the v1.82 release.

Pre-release testing

Here is a zip file of the latest build: https://nextcloud.brashlerphoto.com/s/MicQNZdFNcsk6zq

Remaining Tasks

w7sst commented 1 year ago

I have updated the pre-release version. This build contains all Issues that are currently in code review. Please download the updated zip file: https://nextcloud.brashlerphoto.com/s/MicQNZdFNcsk6zq

@tekenny @ct7aup @f6fvy @scotthibbs @DF9TS @n2ic @jr8ppg @jm1dxh @K6OK

K6OK commented 1 year ago

I tested the build as both a domestic and DX station:

1TT or 100 are shown as entered in the Edit3 box and in the log. ✓ ENN accepted for both domestic and DX in Edit4 box. ✓

With KL7AA (DX) as runner, does not accept 5NN ATT, Aoo, A00 or NN as valid exchanges in Edit4 box.

With K6OK (domestic) as runner, does not reject an invalid state/province (i.e., ZZ or KW) in Edit4 box. It rejects 1TT and 100, but not KW or K.

w7sst commented 1 year ago

Thank you for testing both domestic and DX sides of this contest. I appreciate it.

  1. I updated regular expressions for ATT, Aoo, A00 or NN. Also allow them to be entered into exchange fields. This regex is now: '([0-9]*)|(K)|(KW)|([0-9A]*[OTN]*)'.
  2. For the domestic runner case above, I did changed the regular expression for states/provinces to expect two characters making up US state or VE province: '[ABCDFGHIKLMNOPQRSTUVWY][ABCDEFHIJKLMNORSTUVXYZ]'. This will reject the 'K' or the 'KW' and accept any valid state or province.

I posted an updated build for further testing.

w7sst commented 1 year ago

I posted an updated build containing the Help | First Time Setup. I think this is all the code changes for 1.82 (pending the discussion regarding the ARRL.LIST file).

Please look at the Remaining Tasks at the top of this page. We have the release notes and announcement text remaining. Any help would be welcome. Let's try to get this release announcement completed by 12/12. I will be leaving town on 12/14. Thank you, Mike.

w7sst commented 1 year ago

@scotthibbs - I started the draft Release 1.82. next step is release notes and update the readme.txt file. I'll make a review pass after you get these ready.

@tekenny @ct7aup @f6fvy @scotthibbs @DF9TS @n2ic @jr8ppg @jm1dxh @K6OK We are getting close to releasing 1.82. Please give the release a test drive and test a few contests. Thank you to some of you that have helped with early testing.

Please keep the Remaining Tasks list at the top of this page up to date. Thank you, Mike

K6OK commented 1 year ago
w7sst commented 1 year ago

@K6OK - thank you for the feedback.

w7sst commented 1 year ago

I uploaded an updated build containing these latest changes.

K6OK commented 1 year ago

Good news -- per my phone call with ARRL, permission is granted to use DXCC.LIST under two conditions

  1. MRCE does not market or imply our software is endorsed by ARRL.
  2. ARRL requests that we add a header to the top of DXCC.LIST that says "Used with permission: DXCC Country List, copyright ARRL."
w7sst commented 1 year ago

I uploaded an updated build containing these latest changes.

w7sst commented 1 year ago

Pending review by @k6ok and @f6fvy, I think we are ready to go.

Thank you for all the effort getting this release ready to go.

n2ic commented 1 year ago

Okay, guys, I'm a lid. Just installed Delphi Community Edition. Would like to try that, instead of Lazarus, which is what I used for the current MR running with N1MM+. What's the best way to get the 1.82 source, load it into Delphi, and build it ?

73, Steve, N2IC

On Thu, Dec 8, 2022 at 2:11 AM Mike Brashler @.***> wrote:

Pending review by @K6OK https://github.com/K6OK and @f6fvy https://github.com/f6fvy, I think we are ready to go.

Thank you for all the effort getting this release ready to go.

— Reply to this email directly, view it on GitHub https://github.com/w7sst/MorseRunner/issues/142#issuecomment-1342312751, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD45JRD7CIH3SZCNIYZJR5TWMGQ4NANCNFSM6AAAAAASN2ASHU . You are receiving this because you were mentioned.Message ID: @.***>

K6OK commented 1 year ago

Looks good here. One comment I have, this can wait until the next release if you want, is to make the default startup settings more friendly to the less advanced CW operator, e.g.:

QSK should be unchecked All of the band conditions should be unchecked Default CW speed should be lower than 30 wpm, I'd suggest 25 wpm With VE3NEA as the default call, then the default exchange should be "ON" not "OR" Band conditions: it says LID's but should be LIDs. Possessive apostrophe shouldn't be used here.

As it stands now on first startup the settings might be a little intimidating to a more modest CW op.

Quickly tested all contests with normal exchanges, all seemed OK.

w7sst commented 1 year ago

Hi Steve, Let's point you to our existing documentation for developers. It will be a good opportunity to see if this documentation will answer your questions. Please let us know if it does not or submit changes to fill in the holes.

  1. start with our readme page: https://github.com/w7sst/MorseRunner#how-can-i-help
  2. You will then see:

    Please refer to CONTRIBUTING.md for more information. Developers can refer to DEVELOPERS.md for additional on-boarding information and build instructions.

Let us know how it goes from there...

To directly answer your question, you be doing something like the following to clone a copy of our repository onto your local machine:

git clone https:github.com/w7sst/MorseRunner MorseRunnerCE
cd MorseRunnerCE
git checkout main

Then you can follow the build instructions in DEVELOPERS.md.

n2ic commented 1 year ago

Here's what I get loading it into Delphi CE: [image: image.png]

On Thu, Dec 8, 2022 at 9:39 AM Mike Brashler @.***> wrote:

Hi Steve, Let's point you to our existing documentation for developers. It will be a good opportunity to see if this documentation will answer your questions. Please let us know if it does not or submit changes to fill in the holes.

  1. start with our readme page: https://github.com/w7sst/MorseRunner#how-can-i-help
  2. You will then see:

Please refer to CONTRIBUTING.md https://github.com/w7sst/MorseRunner/blob/main/.github/CONTRIBUTING.md for more information. Developers can refer to DEVELOPERS.md https://github.com/w7sst/MorseRunner/blob/main/.github/DEVELOPERS.md for additional on-boarding information and build instructions.

Let us know how it goes from there...

To directly answer your question, you be doing something like the following to clone a copy of our repository onto your local machine:

git clone https:github.com/w7sst/MorseRunner MorseRunnerCE cd MorseRunnerCE git checkout main

Then you can follow the build instructions in DEVELOPERS.md.

— Reply to this email directly, view it on GitHub https://github.com/w7sst/MorseRunner/issues/142#issuecomment-1342995265, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD45JRBUEMNCJ7U5K3UBTE3WMIFLLANCNFSM6AAAAAASN2ASHU . You are receiving this because you were mentioned.Message ID: @.***>

w7sst commented 1 year ago

Steve, the image did not come through, so I don't see your error.

w7sst commented 1 year ago

Steve, you may have to use the github.com web page to paste an image. If you are sending the image via email response, it may not work.

w7sst commented 1 year ago

I got Steve up and running via direct email.

w7sst commented 1 year ago

Looks good here. One comment I have, this can wait until the next release if you want, is to make the default startup settings more friendly to the less advanced CW operator, e.g.:

QSK should be unchecked All of the band conditions should be unchecked Default CW speed should be lower than 30 wpm, I'd suggest 25 wpm With VE3NEA as the default call, then the default exchange should be "ON" not "OR" Band conditions: it says LID's but should be LIDs. Possessive apostrophe shouldn't be used here.

As it stands now on first startup the settings might be a little intimidating to a more modest CW op.

Quickly tested all contests with normal exchanges, all seemed OK.

@k6ok, The above changes are in code review. I updated the latest build. Thank you again for the input.

w7sst commented 1 year ago

The 1.82 Release has been published. Congrats everyone! Thanks for all the hard work.