Use _pending for the latest changelog entries

[wilzbach]

Regarding #1814 (comment)

A simple solution is to use _pending for the automatically generated changelog. (@MartinNowak) doesn't seem to use the Makefile target here anyways.

Regarding the changelog menu: I wasn't really sure how we should handle the case when a prerelease is progress, so I simply renamed them "Nightlies" as this actually is exactly what the page depicts.

CC @CyberShadow

[dlang-bot]

Thanks for your pull request, @wilzbach!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

[CyberShadow]

Looks like we had the same idea: dlang/phobos#5504 (comment)

[CyberShadow]

Thanks!

The _pre page still has nothing on it to indicate it's not yet released, except the future date and URL, sigh.

[wilzbach]

Hmm any idea what could have went wrong with the deployment?
The changes were properly shown in DAutoTest, but aren't visible on dlang.org, e.g.

http://dlang.org/changelog/2.075.0_pending.html

[MartinNowak]

What was the point of using 2.076.0_pending.html instead of just 2.076.0.html having pending somewhere clearly visible on the page?

[CyberShadow]

I think because update_nav.sh infers the page type from the filename?

[wilzbach]

What was the point of using 2.076.0_pending.html instead of just 2.076.0.html having pending somewhere clearly visible on the page?
I think because update_nav.sh infers the page type from the filename?

Yes, and also it's not trivial to know the future release version of master as this would require detecting the beta tags and this _pending seemed a lot easier.