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

New blog post: "Eclipse Temurin 8u382, 11.0.20, 17.0.8 and 20.0.2 Available" #1997

Closed
smlambert opened this issue Jul 14, 2023 · 1 comment · Fixed by #2014
Closed

New blog post: "Eclipse Temurin 8u382, 11.0.20, 17.0.8 and 20.0.2 Available" #1997

smlambert opened this issue Jul 14, 2023 · 1 comment · Fixed by #2014
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@smlambert
Copy link
Contributor

Blog post title
Eclipse Temurin 8u382, 11.0.20, 17.0.8 and 20.0.2 Available

Determine what content theme this blog post relates to
Release announcement using tags:
announcement,release-notes,temurin

Gather supporting images and media

Release Announcements would contain at least 2 sections:

  • Release notes (which will link to the release notes for each version)
  • New and Notable (which highlights larger changes and/or features of the release)

Set a target publish date
Target publish date as per the Adoptium Content Streams calendar is July 28, 2023

Suggested author
Adoptium PMC

@smlambert smlambert added the documentation Improvements or additions to documentation label Jul 14, 2023
@tellison tellison self-assigned this Jul 25, 2023
@tellison tellison mentioned this issue Jul 25, 2023
4 tasks
@tellison
Copy link
Contributor

Draft created, anyone is invited to change/edit as they see fit.

@github-project-automation github-project-automation bot moved this from Todo to Done in Adoptium 3Q 2023 Plan Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants