Thread overview
why the contradiction on latest version, where is the 2.062 Jan 4, 2013 download ?
Jan 27, 2013
rsk82
Jan 27, 2013
Dmitry Olshansky
Jan 27, 2013
rsk82
Jan 27, 2013
Dmitry Olshansky
January 27, 2013
(I don't know where to ask this, sorry for another topic, I know I was asked not to post here trivial things. But this is not about language itself.)

in download section: http://dlang.org/download.html last version is: http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/dmd.2.061.zip

but http://dlang.org/changelog.html says that last version is: http://ftp.digitalmars.com/dmd.2.062.zip but that link is dead ? So why this inconsistency ?
January 27, 2013
28-Jan-2013 01:10, rsk82 пишет:
> (I don't know where to ask this, sorry for another topic, I know I was
> asked not to post here trivial things. But this is not about language
> itself.)
>
> in download section: http://dlang.org/download.html last version is:
> http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/dmd.2.061.zip
>

That's the right one.

>
> but http://dlang.org/changelog.html says that last version is:
> http://ftp.digitalmars.com/dmd.2.062.zip but that link is dead ? So why
> this inconsistency ?

Because nobody fixed this bogus changelog entry... Was reported a couple of times and indeed it's very embarrassing that it still mentions 2.062 as if it was released and features a broken link.

-- 
Dmitry Olshansky
January 27, 2013
On Sunday, 27 January 2013 at 21:14:51 UTC, Dmitry Olshansky wrote:
>and features a broken link.

And what about the features listed in this bogus entry ? Are they in latest legitimate version or the new upcoming ?
January 27, 2013
28-Jan-2013 01:18, rsk82 пишет:
> On Sunday, 27 January 2013 at 21:14:51 UTC, Dmitry Olshansky wrote:
>> and features a broken link.
>
> And what about the features listed in this bogus entry ? Are they in
> latest legitimate version or the new upcoming ?

These just list the bugs fixed since the last release it seems. So they are coming into 2.062, yes. The bogus part is that there shouldn't be 2.062 entry or it should be marked as alpha/in-progress with a proper link to the current nightly-build. Thinking more of it the latter is a better idea.

-- 
Dmitry Olshansky