Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linking Medley releases from Interlisp.org #1681

Open
pamoroso opened this issue Apr 25, 2024 · 5 comments
Open

Linking Medley releases from Interlisp.org #1681

pamoroso opened this issue Apr 25, 2024 · 5 comments

Comments

@pamoroso
Copy link
Contributor

A suggestion by @MattHeffron in the April 24, 2024 external meeting is to link from the News and Status Reports page of Interlisp.org to the releases page of Medley's GitHub repo. This way users can learn the latest updates about development, download the system, and get an idea of the progress and activity of the project.

@pamoroso
Copy link
Contributor Author

PR #220 addresses this issue.

@pamoroso
Copy link
Contributor Author

I'm closing this issue addressed by PR #220.

@masinter
Copy link
Member

Usually, "news" information should be in reverse chronological order, except for permanent items (like this one). I would expect it to be pinned at the top since it's likely to be the 'most recent' news perpetually.

It happens that the latest release of Medley is having trouble in Windows 'native'-- @skaisler1 noted problems with the 'release'. I don't think the problem affects other platforms. I think we might want to caution people who want to pick up the latest.

@pamoroso
Copy link
Contributor Author

What sections should be pinned? Here's a possible ordering (numbers added for clarify)

  1. Build Notes
  2. [latest year] Annual Report released!
  3. Annual Reports
  4. [other sections in reverse chronological order]

Also, I'd change the formatting of "2023 Annual Report released!" from # to ## to match the other headings at the same level. If # was added for emphasis, the position of the heading in the sequence gives it enough emphasis.

@pamoroso
Copy link
Contributor Author

PR #222 shows what these possible changes look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants