Bug 17644 – [Downloads] Bad link to changelog for DMD beta version.

Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P3
Component
dlang.org
Product
D
Version
D2
Platform
All
OS
All
Creation time
2017-07-13T06:25:46Z
Last change time
2017-12-16T02:59:53Z
Keywords
pull
Assigned to
No Owner
Creator
Gerald Jansen

Comments

Comment #0 by jansen.gerald — 2017-07-13T06:25:46Z
DMD Beta 2.075.0-b4 Changelog link: https://dlang.org/changelog/2.075.0.html gives 404 Not Found.
Comment #1 by greeenify — 2017-07-13T07:12:08Z
Comment #2 by greensunny12 — 2017-07-13T09:00:59Z
Comment #3 by jansen.gerald — 2017-07-13T17:05:35Z
(In reply to Seb from comment #2) > PR: https://github.com/dlang/dlang.org/pull/1820 How can I see the effect of these changes on a copy of the site? I have cloned dlang.org and successfully built it. How can I clone your branch/changes? (sorry for the git/github newbie question)
Comment #4 by greeenify — 2017-07-13T17:15:15Z
> How can I see the effect of these changes on a copy of the site? The simplest way is clicking on DAutoTest at the PR status page. DAutoTest builds the entire website, shows the diff between the changes and allows to preview changes > How can I clone your branch/changes? There are many ways. One is: git remote add https://github.com/Wilzbach/dlang.org git fetch wilzbach git checkout wilzbach/download-version (I'm currently on my phone, so I hope there wasn't a typo. Don't hesitate to ask again if you have further questions)
Comment #5 by greeenify — 2017-07-13T17:22:03Z
> How can I clone your branch/changes? Btw the guidelines for maintainers might answer a few of your questions and it contains a handy git shortcut if you happen to clone a PR more than once: https://wiki.dlang.org/Guidelines_for_maintainers
Comment #6 by jansen.gerald — 2017-07-13T17:31:41Z
(In reply to greenify from comment #5) > > How can I clone your branch/changes? > https://wiki.dlang.org/Guidelines_for_maintainers Thanks for the tips!
Comment #7 by greensunny12 — 2017-12-16T02:59:53Z
I will close this as fixed now because the changelog generation has undergone quite a few changes over the last months and so far it seems to have gone smooth. I will keep an eye on this for the next beta & release. Thanks!