Engdocs 2335b #21809
Engdocs 2335b #21809
Conversation
aevesdocker
requested review from
craig-osterhout and
sarahsanders-docker
as code owners
github-actions
bot
added
area/hub
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| ### New | ||
|
|
||
| - Beta: You can now create [organization access tokens](/security/for-admins/access-tokens/) (OATs) to enhance security for organizations and streamline access management for organizations in the Docker Admin Console. |
There was a problem hiding this comment.
see previous comment. it might be helpful to use consistent styling across summary bar and inline references to release lifecycle so the reader becomes familiar with the iconography and styling across the docs site
There was a problem hiding this comment.
Yes defo! Noted!
| This page provides details on new features, enhancements, known issues, and bug fixes across Docker Home, the Admin Console, billing, security, and subscription functionalities. | ||
|
|
||
| Take a look at the [Docker Public Roadmap](https://github.com/orgs/docker/projects/51/views/1?filterQuery=) to see what's coming next. | ||
|
|
There was a problem hiding this comment.
Should Personal access tokens (PATs) now support expiration dates be included on this page?
There was a problem hiding this comment.
Added it because it's related to security and this RN covers security as well
sarahsanders-docker
left a comment
sarahsanders-docker
left a comment
There was a problem hiding this comment.
Overall, I like this approach and feel that having one release notes section to encapsulate "Platform" is a sound approach. I don't see anything missing from the release notes as of now.
Not a blocker, but I left two comments about standardizing how we reference release lifecycle stages in docs. With the introduction of the summary bar, I think it could be useful to define how we reference release lifecycle stages in the style guide, and use that consistently across docs.
|
LGTM Off the top of my head, there's probably a lot more we can add here that had no place when they were originally released. Nice to have but not necessary in this PR.
|
Ah yes! Would you be able to add these in a follow-up? Not sure I have the correct dates on these items |
<!--Delete sections as needed --> ## Description Added some backdated platform features to the new release notes. - Docker Home - Consolidated subscriptions - Org insights ## Related issues or tickets Follow up to #21809 ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Editorial review --------- Signed-off-by: Craig <[email protected]> Co-authored-by: Sarah Sanders <[email protected]>
3 participants
Description
This PR reorganizes some of the Docker Hub release notes (RN) content, moving it into a separate, dedicated Platform release notes section.
With the introduction of a distinct Platform section in the docs, encompassing its own products, certain content from the Docker Hub release notes no longer applies. Similarly, some updates from the Docker Desktop release notes are better highlighted in the new Platform RN.
As more features are added to the Admin Console, Docker Home, and security, billing, subscrption products, this new release notes section will serve as a central hub for updates and fixes, making it easier for admins to stay informed.
Related issues or tickets
Reviews