Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev 1.1.0 (AiMesh Beta) as next Release #189

Merged
merged 78 commits into from
Apr 8, 2024
Merged

Dev 1.1.0 (AiMesh Beta) as next Release #189

merged 78 commits into from
Apr 8, 2024

Conversation

ExtremeFiretop
Copy link
Owner

@ExtremeFiretop ExtremeFiretop commented Apr 8, 2024

MerlinAU Version 1.1.0 released.

What's Changed/Fixed?:

PR: #179
Include AiMesh Node Versions. Long discussed, long asked. I broke some brain cells over this one.
No, it does not flash the nodes from the primary, it does however check any AiMesh nodes for updates and sends a summary email for any updates available.. You still need MerlinAU for each node you wish to auto-update.
Meaning you can disable email notifications on each node, and only get one email from the primary instead of one per node.
AiMesh Nodes menu will be disabled on anything but the primary router.

PR: #183
Improvements for better estimation of "Available RAM", we identified the current method was too conservative, we now have an improved estimation. (Thanks @Martinski4GitHub)!

PR:#184
Fixes & code improvements for new AiMesh Nodes feature (Thanks @Martinski4GitHub)!

PR:#187
Code improvements to minimize the number of NVRAM calls (Thanks @Martinski4GitHub)!

Tightening up some code & general code improvements with PRs in-between.
As always, we highly recommend you update whenever possible. Enjoy the new release! :)

ExtremeFiretop and others added 16 commits April 6, 2024 21:11
This reverts commit 98207c5.
Made fixes & added code improvements in the new code handling AiMesh Nodes.
Fixes & code improvements for Mesh Nodes
This reverts commit 6215d0a, reversing
changes made to c009a38.
A few code improvements to minimize the number of NVRAM calls for a couple of settings that should not change often, especially during script execution.
@ExtremeFiretop ExtremeFiretop added bug Something isn't working enhancement New feature or request labels Apr 8, 2024
@ExtremeFiretop ExtremeFiretop enabled auto-merge April 8, 2024 04:44
@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub

Your good to go when ever, as per the last release, we are confirming nothing is blocked (Once you approve!)
Once you approve this, and nothing is confirmed blocked, we still need to validate the release and tagging works as expected.

@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub

Updated the forum post to reflect your modification :)

@Martinski4GitHub
Copy link
Collaborator

MerlinAU Version 1.1.0 released.

What's Changed/Fixed?:
....

PR: #183 Improvements for better estimation of "Available RAM", we identified the current method was too conservative, we now have an improved estimation. (Thanks @Martinski4GitHub)!

I modified the description above. Accuracy refers to the measurement of the actual value. What we have is an improved estimation of the amount of "Available RAM." I know it seems pedantic but in engineering the words "accuracy" & "precision" have clear & exact meanings that are more limited than when used in everyday conversation.

Copy link
Collaborator

@Martinski4GitHub Martinski4GitHub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to go live!

@ExtremeFiretop ExtremeFiretop merged commit 15369ef into main Apr 8, 2024
5 checks passed
@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub

YAHOOOO!! NOW we are cookin with fire!
Wheres the BBQ grill I need a steak on this heat.

Seems like once you approved it instantly pushed using the auto-merge this time!
ANND we got our release and tag as expected.

Plus between the last PR for Gnuton and learning how to "update" the branches I think we are over the learning curves now.

@Martinski4GitHub
Copy link
Collaborator

@Martinski4GitHub

YAHOOOO!! NOW we are cookin with fire! Wheres the BBQ grill I need a steak on this heat.

Or, as my Father would say: "NOW, we're really cooking with gas!!"

Seems like once you approved it instantly pushed using the auto-merge this time! ANND we got our release and tag as expected.

Yeah, once approved, it just did everything else automatically. Excellent job on that automation front, Bud!!
Releasing new version updates will be a breeze from now on. :>) :>)

@ExtremeFiretop
Copy link
Owner Author

@Martinski4GitHub
YAHOOOO!! NOW we are cookin with fire! Wheres the BBQ grill I need a steak on this heat.

Or, as my Father would say: "NOW, we're really cooking with gas!!"

Seems like once you approved it instantly pushed using the auto-merge this time! ANND we got our release and tag as expected.

Yeah, once approved, it just did everything else automatically. Excellent job on that automation front, Bud!! Releasing new version updates will be a breeze from now on. :>) :>)

Thanks buddy!
That was the idea, the less manual process the better, easier on us!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants