Update release pages

[bmribler]

• Added HDFview 3.4.0 page
• Added an entry for 1.14.6 release
• Fixed typos

[bmribler]

@lrknox @loricooperhdf
Do you think this one is good to be merged?

[lrknox]

The release date will need to be updated when it actually happens (early next week, hopefully). If the page is merged, does it automatically become public, or is there a release/publish step to move it to support? I think we can't post a release date in the past when it hasn't happened yet, but if it's not public, it should be ok. Larry

…

________________________________ From: bmribler ***@***.***> Sent: Friday, January 2, 2026 9:57 AM To: HDFGroup/HDFGroup.github.io ***@***.***> Cc: Larry Knox ***@***.***>; Mention ***@***.***> Subject: Re: [HDFGroup/HDFGroup.github.io] Update release pages (PR #378) [https://avatars.githubusercontent.com/u/39579120?s=20&v=4]bmribler left a comment (HDFGroup/HDFGroup.github.io#378)<#378 (comment)> @lrknox<https://github.com/lrknox> @loricooperhdf<https://github.com/loricooperhdf> Do you think this one is good to be merged? — Reply to this email directly, view it on GitHub<#378 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADGMWCUYUJAUL74HH7KDA2L4E2IOBAVCNFSM6AAAAACQCO23M2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBVGY2DIMJUGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[lrknox]

Unless I'm wrong (and I tried it) the process to install an HDFView application image such as HDFView-3.4.1App-Windows.zip is to extract the binary file where desired. Maybe line 31 would be more accurate if it were something like this? "Using an application image. This method simply requires extracting the downloaded HDFView-3.4.1App*.tar.gz or .zip file in the chosen install location."

[bmribler]

Done

[bmribler]

Should I change the release date again? Although the date on the github release is 1/27.

[brtnfld]

Since this is a markdown file, I would prefer not having to keep updating this manually by doing something like:

Dynamic Badges

Recommended. This replaces your text with dynamic images from Shields.io that pull directly from your GitHub repo's metadata. You never have to touch the file again.

Replace your table content with these Markdown image links:
code Markdown

## Release Information

| Version | Release Date |
| :--- | :--- |
| ![GitHub release (latest by date)](https://img.shields.io/github/v/release/YOUR_USERNAME/YOUR_REPO?label=HDFView&color=white) | ![GitHub Release Date](https://img.shields.io/github/release-date/YOUR_USERNAME/YOUR_REPO?label=&color=white) |

    Replace YOUR_USERNAME and YOUR_REPO with your actual details.

    Note: The &color=white parameter makes the background blend in with most READMEs, making it look like text rather than a "badge."

[bmribler]

@brtnfld but the Newsletter says 1/30 which is different from the GH release. Should I still go with the GH release?

Update: From your suggestion, I got it now, go with the GH release. Sorry.

[bmribler]

It's not perfect, but I think it's ok for now. Thoughts?