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

[release] please include the version in your release files #1315

Open
arrowgent opened this issue Jan 29, 2025 · 1 comment
Open

[release] please include the version in your release files #1315

arrowgent opened this issue Jan 29, 2025 · 1 comment
Labels
state:Backlog This issue will be worked on in the future type:Enhancement New feature or request

Comments

@arrowgent
Copy link

arrowgent commented Jan 29, 2025

Is your feature request related to a problem? Please describe.

go to releases
click 6.x.x

Describe the solution you'd like

download video2x_aplusb_v6.x.x.thing

Describe alternatives you've considered

putting versions in the filename helps keep things organized

Additional context

linux testing 6.4.0 appimage

thanks

@arrowgent arrowgent added the type:Enhancement New feature or request label Jan 29, 2025
@github-actions github-actions bot added the state:Backlog This issue will be worked on in the future label Jan 29, 2025
@k4yt3x
Copy link
Owner

k4yt3x commented Jan 30, 2025

I've considered this before. It's currently not done like that because it introduces extra complexity in the pipelines.

Let's say I want to write a release pipeline (and I plan to do so), if I were to include the version in the output file name, I will have to somehow parse the version from either Git tag or the header files. All the build scripts (e.g., AUR) will also have to adapt and use the version number in the URLs twice. If I don't put version numbers into the file names then they can all just be static, less complexity.

However, you do have a point. I agree it'll be convenient for end users. Let me think about this for a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:Backlog This issue will be worked on in the future type:Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants