On Jun 8, 2013, at 1:43 AM, Marcus Denker <[email protected]> wrote:
> > On Jun 7, 2013, at 8:03 PM, [email protected] wrote: > >> Marcus Denker wrote: >>> Hi, >>> >>> I changed all links to point to the latest 2.0 build on files.pharo.org >>> >>> Reason: >>> >>> -> We are fixing bugs, yet people downloading 2.0 do not see the fix >>> -> We had multiple times that people wasted quite some effort >>> re-reporting bugs >>> that are already fixed. >>> >>> Notes >>> -> the file name "latest.zip" is not good for the image. It should >>> encode that it is the image only and the version number maybe? >>> -> I did not change any VM related download links, but I think we >>> should do the same there. >>> >>> >>> Marcus >>> >> That is great that 2.0 is continuing to improve. >> >> +100 for including version numbers on the web page - something like [1]. >> For the purpose of reproducibility and least surprise, at [2] where it >> currently says "2.0 (release)" and "Pharo2.0 (win)" I would expect that >> link to download the _exact_ same file every time, except today that zip >> file contains files dated today, so obviously is not the same file as last >> week. You might get away with following "latest" with a link called "Pharo2 >> (win)" without the minor-version number, but by including a a minor-version >> number I would expect that it is the constant point-in-time snapshot of the >> _2.0 release_. > This is what we had. But we fixed bugs already, yet people where reporting > those bugs again. So what do we do? We can *not* change the link for every > update… I spend already today around 30 minute to fix all the links. Should I > do that > every time we do an update? To explain: We have the major version Pharo2 Pharo3 Pharo4 These are released once per year. While developing, we do updates. At some point (e.g. #553) we release. Then we continue to do do updates. So Pharo images are always 100% identifiable by Major+UpdateNumber. When you go to pharo.org, you download the *latest* update. Else we end up getting bug reports for already fixed issues constantly (this happend now already multiple times, and I feel to bad that someone takes such a huge effort to report a bug that we fixed weeks ago). If you want to re-download the version you go weeks ago, there is http://files.pharo.org/image/20/ with a complete history, and it is very easy to download exactly what you downloaded weeks ago, yet all the new people get the newest download. Marcus
