Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
x/website: include release date on dl page #40488
@broady it looks like we have this information present in internal/history/release.go, I'd be happy to take a stab at trying to include that on the DL page, but the DL page appears to take memcache + cloud datastore as hard dependencies and I'm not sure how to bootstrap either the memcache or cloud datastore locally; it doesn't look like there are docs for those?
Copying a comment from the CL:
That looks somewhat inconsistent with the rest of the design of the golang.org website to me. It's not a complete English sentence.
If we're going to do this, I would suggest we consider either putting the date into the header, similar to how it's done on the release history page:
An alternative to consider would be to include an entire paragraph that states the release date and describes the release (using information from the
However, I'm not sure this is an improvement. It copies information from the release history page, which already exists. It seems the download page should focus more on the downloads rather than duplicating what's on the release history page.
I'm more okay with just the date in the header, but given the complexity/size of the change, I'd like to see more arguments for why this is a good change for users first. Can you elaborate on why consulting the release history page doesn't work well? Thanks.
@andybons What do you think about this?
I'm convinced that adding the release date to the https://golang.org/dl/ page is worth doing, even though this information is available on the release history page, because of the rationale you elaborated on. Let's agree on how it should look.
My concern is that the current design, as far as I can tell, looks like no other element of the website (due to the smaller font, being an incomplete sentence, using a different date format). Please let me know if I missed some page which you used as a reference. Otherwise, are you okay with trying to get something that looks more consistent with the rest of the golang.org website? I've made some suggestions in comments above.