Issue #1119
closedInclude build (release) number in download filename
0%
Description
I would welcome it if the file names would include the build version as well. Although this can be distinguished easily on the replicant server from the directory structure, users have to rename files on their own if they want to keep several downloaded replicant versions for one device in the same directory.
Current naming: replicant-4.2-crespo.zip
Suggested naming: replicant-4.2.0003-crespo.zip
Updated by Paul Kocialkowski over 9 years ago
- Status changed from New to Rejected
- Resolution set to wontfix
Well, that wouldn't be very convenient for our release scripts and overall, it doesn't seem very relevant. See it as an executable binary: you don't change its name with every version. In order to keep everything clear, I suggest you store each version in specific folders that make the version explicit, as it is done in our releases.
Updated by Daniel Kulesz over 9 years ago
Okay. But while this is true for binaries, release archives from projects usually carry the version number in its name. This is true for replicant as well, but only for major release numbers which I find rather inconvenient. I see your argument that it takes some work (probably better spend elsewhere) to change the release scripts, but if this is the only argument maybe you could leave this ticket open for sometime later?
Updated by Paul Kocialkowski over 9 years ago
Well, this is true, and there is already the version number "4.2" in the archive, so my point wasn't very relevant. Nevertheless, it does take work to do that, and if we start doing it for the zips, why not for the rest (recovery.img, tools, etc)? the release numbers refer to a particular state of the code and I just don't feel like it's relevant to mention it on the file names.