Show messages boxes for beta and nightly#1821
Conversation
|
Thanks for your pull request, @wilzbach! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. |
| $(CHANGELOG_NAV_LAST 2.074.1) | ||
|
|
||
| $(VERSION Jul 16, 2017, =================================================, | ||
| $(BETA_VERSION Jul 16, 2017, =================================================, |
There was a problem hiding this comment.
To avoid doing this manually, there will be --release-type=beta (dlang/tools#251)
| ) | ||
| $4 | ||
| ) | ||
| VERSION=$(STABLE_VERSION $0) |
There was a problem hiding this comment.
For compatibility, in a follow-up we could do a quick sed to remove this.
| $(MESSAGE_BOX red, Unstable - nightly releases are not suited for production. Use stable.) | ||
| ) | ||
| $4 | ||
| $3 |
There was a problem hiding this comment.
In dlang/tools#251 the format is unified, that's why the tools PR needs to be pulled first.
| } | ||
|
|
||
| /** | ||
| * Message boxes - different color for each category |
There was a problem hiding this comment.
As it turns out even without #1778, the message boxes are universally useful.
| MENU_W_SUBMENU = <li class='expand-container'><a class='expand-toggle' href='#'><span>$0</span></a> | ||
| MENU_W_SUBMENU_LINK = <li class='expand-container'><a class='expand-toggle' href='$1'><span>$+</span></a> | ||
| MENU_W_SUBMENU_END = </li> | ||
| MESSAGE_BOX = $(DIVC message-box message-box-$1, $+) |
There was a problem hiding this comment.
We might define RED_MESSAGE_BOX or ERROR_MESSAGE_BOX etc. in the future, but for now I kept it as bloat-free as possible.
| changelog/${NEXT_VERSION}_pending.dd: | ${STABLE_DMD} ../tools ../installer | ||
| $(STABLE_RDMD) $(TOOLS_DIR)/changed.d $(CHANGELOG_VERSION_MASTER) -o $@ \ | ||
| --version "${NEXT_VERSION} (pending)" --date "Pending" --nightly | ||
| --version "${NEXT_VERSION} (Nightly)" --date "To be released" --release-type "nightly" |
There was a problem hiding this comment.
Nightly is more meaningful than "pending"
|
TBH the boxes seem too much to me. Not only are they really distracting (at least as they are in your screenshots), but the changelog is not the place for telling the user how (not) to use a version. I would suggest a much simpler, subtler change - enough that people are not going to be confused about the changelog of a yet-unreleased version. |
Sure, we can insert anything we want there once we have specific templates from the changed tool. |
|
I like the idea to add extra information such as "report bugs to |
Yep, just to clarify - currently on http://dlang.org/changelog/2.075.0_pre.html the only clues that this is the pending changelog of a yet-unreleased version is the URL and the (for now) future date. |
That got broken with #1817 as it's using the generic make rule now, it used to say |
Aaaah. Sorry.
Hmm, that's a fair concern, though when the content of the page is bound to change, keeping the links working isn't as important, as an old link will not point to the version of the page at the time when the link was created anyway. I think we can go with a |
Huh? @MartinNowak don't you commit the https://web.archive.org/web/20170703054803/https://dlang.org/changelog/2.075.0.html -> "to be released Jul 9, 2017" We could, of course, always generate |
Read the Makefile ;), we were using different macros for those changelogs. IMO a better mechanism than hardcoding differences into the changed tool. There are two parts that need to happen for a proper pending changelog during beta. We need to get a proper NEXT_VERSION. I can write the current beta and the latest version to the dlang.org repo, or we might use dmd's VERSION file which is now updated like We need to purge the changelog in time. I'd suggest we extend the changed tool so that it can append new loose changelog entries to a committed |
|
Ping on this, just pulling of the NEXT_VERSION based on dmd/VERSION should be fairly straightforward. |
|
BTW, quite a nice changelog. Might be a nice idea to combine all the changelog TOCs on the index page. Not sure how they produce the overall points, maybe some fancy burndown planning, but that doesn't carry too much value IMO. |
|
Fair enough, let's close this then. |


dlang/tools#251 needs to be pulled first.