Don't overwrite the weekly alpha release.

[ndgnuh]

Currently, when a new weekly alpha build is out, the old one is overwritten.

I suggest adding a commit hash after release name and do a separate release (like the one of the image below). This way it will be easier to track the problems (if there's any) and revert to the working version.

Or use release date

[hqnghi88]

the name of the packages do the job, however we can add as your suggestion, the suffix into the name of release

[ndgnuh]

I mean that we create a new release, and don't overwrite the old one. There would be Alpha Version 1.8.2_thisweek and Alpha version 1.8.2_nextweek and so on. If something does happens, users can just download the latest working version.

[hqnghi88]

ok, NO for that, for many reason and we dont create such kind of release.

[ndgnuh]

Can you explain why?

[AlexisDrogoul]

Hi, the main reason is that the activity in terms of release is really important during intense coding periods (and we are going to enter one with GAMA 1.8.2), during which it doesn't really make sense to ask users to download GAMA every week ad there might be very big bugs and issues. The ones really interested in following are usually the developers themselves (and they know how to build GAMA from source). Otherwise, the differences between two weekly versions is too small to justify keeping the old ones. Last reason may seem less important but is nevertheless something we will need to pay attention to in the future: keeping old versions is a waste of resources and energy and we should try (collectively of course) to be more frugal in terms of digital resources.