Quote from: CaptDero on June 08, 2018, 02:56:24 PM

Quote from: fellestreum on June 08, 2018, 12:23:51 PM

Quote from: pegos on June 08, 2018, 11:17:17 AM

Quote from: fellestreum on June 08, 2018, 10:11:13 AM

I think when you are in alpha version and almost constantly producing new builds, it just slows you down keeping track of file naming versioning

I have nothing to add, I know exactly what I'm writing, 20 years a day I'm producing a code.
I do not know exactly what you are advocating.
xxx_001, xxx_002, xxx_003 ....?
it is enough to note the working name in the description in download page
I will not participate in the wacky wars!
I write these remarks because I am interested in the project being developed in the right direction, based on personal experience.

Ok, fine, no problem, not trying to pick a fight. Just trying to offer a rational explanation for observed behaviour. I imagine the dev team are working under extreme time pressure right now and are just not doing stuff they consider non-essential. However if you have different explanation for observed behaviour feel free to offer it.

@pegos, you are absolutely right. As @fellestreum said is right but will definitely add in coming releases.

Actually I think it is better to keep the filenames static with these alpha builds that are updated often.

It makes it easier to update, when you know a new release is out, you just run the same command again

wget http://seeds.dero.io/testnet/dero_linux_amd64.tar.gz

(or whatever works for your version) without needing to check the new filename and change the command possibly across multiple systems or in a script etc