starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-25 23:25:54 +03:00

[GH-ISSUE #1447] Documentation: Add release number to Downloads page #1996

New issue

Closed

opened 2026-03-01 18:37:52 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 18:37:52 +03:00

Owner

Originally created by @hseg on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1447

Is your feature request related to a problem? Please describe.
When opening #1446, I noticed the release number under consideration appears nowhere, so my explanation of the situation is unclear. It would make communication clearer if I could cite a version number.

Describe the solution you'd like
On the Downloads page (and in the links to the download images), add the release number of the images.

Describe alternatives you've considered
None -- did consider that one reason not to version is to avoid miscommunicating the message that the images need to be updated on each new release of the distros, but that seemed an insufficient reason to me

Additional context
This is in contrast to any other project I've encountered, was surprised when I realised this was the case.

Originally created by @hseg on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1447 **Is your feature request related to a problem? Please describe.** When opening #1446, I noticed the release number under consideration appears nowhere, so my explanation of the situation is unclear. It would make communication clearer if I could cite a version number. **Describe the solution you'd like** On the Downloads page (and in the links to the download images), add the release number of the images. **Describe alternatives you've considered** None -- did consider that one reason not to version is to avoid miscommunicating the message that the images need to be updated on each new release of the distros, but that seemed an insufficient reason to me **Additional context** This is in contrast to any other project I've encountered, was surprised when I realised this was the case.

kerem

2026-03-01 18:37:52 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-01 18:37:52 +03:00

Author

Owner

@antonym commented on GitHub (May 25, 2024):

Clarified downloads page here:

https://netboot.xyz/downloads/

All releases on that page are rolling and are updated on every commit to this repo. If you are looking for more stable versions, they can be downloaded here.

The versions from operating systems change often so breakage does occur, so it's usually recommended to use either the latest rolling or release version to get the best experience.

@antonym commented on GitHub (May 25, 2024): Clarified downloads page here: https://netboot.xyz/downloads/ All releases on that page are rolling and are updated on every commit to this repo. If you are looking for more stable versions, they can be downloaded [here](https://github.com/netbootxyz/netboot.xyz/releases). The versions from operating systems change often so breakage does occur, so it's usually recommended to use either the latest rolling or release version to get the best experience.

kerem commented

2026-03-01 18:37:53 +03:00

Author

Owner

@hseg commented on GitHub (May 25, 2024):

That doesn't really address my issue - yes, the situation is clearer now, but I still have no way of determining the commit the rolling release is based on, making reporting issues more difficult.

(However, the link to the stable releases page is appreciated, and would've probably prevented me from even going down this script path to begin with!)

I see you're using static hosting, though. Is it that you don't have a way of/don't want to interpolate the commit hash into the page? In that case, is it at least possible to eh have the plain https://boot.netboot.xyz/ipxe/netboot.xyz.iso link redirect to https://boot.netboot.xyz/ipxe/netboot.xyz-v42-beeffeed.iso, perhaps by symlinking the two on the server? An alternative is to use a Content-Disposition header, but that's less clear and probably more work.

El 25 de mayo de 2024 22:38:37 GMT+03:00, Antony Messerli @.***> escribió:

Clarified downloads page here:

https://netboot.xyz/downloads/

All releases on that page are rolling and are updated on every commit to this repo. If you are looking for more stable versions, they can be downloaded here.

The versions from operating systems change often so breakage does occur, so it's usually recommended to use either the latest rolling or release version to get the best experience.

--
Reply to this email directly or view it on GitHub:
https://github.com/netbootxyz/netboot.xyz/issues/1447#issuecomment-2131414482
You are receiving this because you authored the thread.

Message ID: @.***>

@hseg commented on GitHub (May 25, 2024): That doesn't really address my issue - yes, the situation is clearer now, but I still have no way of determining the commit the rolling release is based on, making reporting issues more difficult. (However, the link to the stable releases page is appreciated, and would've probably prevented me from even going down this script path to begin with!) I see you're using static hosting, though. Is it that you don't have a way of/don't want to interpolate the commit hash into the page? In that case, is it at least possible to eh have the plain <https://boot.netboot.xyz/ipxe/netboot.xyz.iso> link redirect to <https://boot.netboot.xyz/ipxe/netboot.xyz-v42-beeffeed.iso>, perhaps by symlinking the two on the server? An alternative is to use a Content-Disposition header, but that's less clear and probably more work. El 25 de mayo de 2024 22:38:37 GMT+03:00, Antony Messerli ***@***.***> escribió: >Clarified downloads page here: > >https://netboot.xyz/downloads/ > >All releases on that page are rolling and are updated on every commit to this repo. If you are looking for more stable versions, they can be downloaded [here](https://github.com/netbootxyz/netboot.xyz/releases). > >The versions from operating systems change often so breakage does occur, so it's usually recommended to use either the latest rolling or release version to get the best experience. > >-- >Reply to this email directly or view it on GitHub: >https://github.com/netbootxyz/netboot.xyz/issues/1447#issuecomment-2131414482 >You are receiving this because you authored the thread. > >Message ID: ***@***.***>

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#1996

No description provided.

Rows
Columns