Problem/Motivation
This issue will track the path to marking the Announcements Feed module stable. The initiative is outlined in #2940739: Project messaging channel in core initiative
Proposed resolution
Fix the following issues:
- #3206643: Project messaging channel in core (as experimental)
- #3356482: Add help topic for Announcements Feed module
- #3356515: Give users a way to access announcements if toolbar module is disabled
Not a stable blocker, but important for a future iteration
These would be ideal but have a dependency on the new "dashboard" functionality (issue here: #3244581: Enhance user experience with customizable dashboards):
- #3349394: Provide announcement feed as a block
- #3356486: Indicate which announcements are new and allow a user to mark an announcement as read
- #3355396: Once announcements feed is converted to Dashboard, implement standardized notifications
Remaining tasks
All blocker issues above complete!
- Mark stable
User interface changes
The announcements feed will appear in the top of the admin toolbar
API changes
n/a
Data model changes
Release notes snippet
Drupal core now includes an announcements feed of project news from Drupal.org. This module was introduced as an experimental core module in Drupal 10.1.0, but is now stable and ready for production use!
This feed of announcements is displayed in the Drupal administrative toolbar to site owners/editors, tracking read/unread status with cache tags. Announcements may include: news about upcoming Drupal features, important information for site owners on older Drupal versions, and information about supporting the Drupal project through Drupal Association programs, etc. Announcements can be seen by users with the "View drupal.org announcements" permission.
The feed is also accessible through a link under the /admin route and is also part of the help info of the module.
Issue fork drupal-3356488
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3356488-announcements-feed-path
changes, plain diff MR !5274
Comments
Comment #2
fjgarlin commentedComment #3
aaronmchaleI would recommend adding #3349394: Provide announcement feed as a block
Comment #4
fjgarlin commentedAgree. Two of the issues depend on the "dashboard" functionality being implemented. I made that clear in the issue description.
Comment #5
fjgarlin commentedComment #7
hestenetComment #8
hestenetI believe this is RTBC - and ready for project announcements to be marked Stable.
There are follow ups for Dashboard but they can happen as part of the Dashboard work directly.
Comment #11
bramdriesenNot 100% sure if this is "the" issue, but created a MR to actually mark the module as stable.
Comment #12
longwaveThis looks good to me - all blockers are fixed, the module is small and self contained and we haven't had reports of any issues, so I think this is good to go in 10.2.0.
Comment #13
andypostI bet it needs CR and probably release notes snippet
Comment #14
bramdriesenI can do that :)
Comment #15
bramdriesenNot re-inventing the weel, re-used most of the text from when the module was added as experimental. Feel free to adopt where needed.
Change record: https://www.drupal.org/node/3399817
Comment #16
lauriiiTagging with the appropriate tags to get this approved.
Comment #17
catch+1 from me. Pretty self contained and got a fair bit of review when we initially committed it.
Comment #18
larowlanReviewed this extensively when it went in. Happy to remove the FM tag.
Do we have an issue to add this to the standard profile?
Comment #19
bramdriesenNo I don’t think so.
You want to add it here?Guess it's better to split, created #3401753: Add Announcements Feed to the Standard profileComment #20
larowlanA follow up issue is fine
Comment #21
andypost+1 rtbc as follow-up added
Comment #22
xjmIncreasing the stability of modules also requires RM review, so tagging for that too.
Comment #23
lauriii@xjm FWIW, I didn't tag it with needs release manager review because this received RTBC from @longwave and @catch +1'd this in #17.
Comment #24
catchIt's tricky when the tag is never added because then you can't ctrl-f for it being removed, but yeah officially removing it now since both me and @longwave have +1d already.
Comment #25
catchAlso I don't think this needs FEFM review, that would only be the case if it was bringing in new js libraries or API, neither of which it does, so removing the tag on their behalf.
Comment #26
bramdriesenCool only Product manager review left then.
Btw, is there a documentation page about those tags? I can't quite wrap my mind around which one to add when 😅 it's just gut instinct based on issues I've seen. I ended up here: https://www.drupal.org/node/2457875#faq-tags but that only shows which tags there are, not really when to use them. Some explanation is shown when hovering over the tag when it's added, but yeah that only works when they are added and saved to the issue.
Comment #27
longwave@BramDriesen see https://www.drupal.org/docs/develop/issues/fields-and-other-parts-of-an-...
Comment #28
bramdriesen@longwave Thanks! Bookmarked 😇
Comment #29
xjm@lauriii In the future it'd be helpful to ask the individual whether they're formally signing off or not; sometimes a +1 is just an individual opinion and other times it's a signoff. :) Also, adding the tag gives others in the role (like me) a chance to see the issue if they did not before.
@longwave and @catch mention code reviews, but not any evaluation of the module's technical debt. I checked that to be safe and the very pleasant result is "there isn't any":
https://www.drupal.org/project/issues/search/drupal?project_issue_follow...
Two things I've wished for from the announcements feed are improving the governance of what goes in, and also making it a bit less "break glass in case of emergency, drumm runs a drush command" to get new announcements out. However, neither of those things need to be stable blockers. So I'm fine with it being marked stable also.
Additionally, we should add this to Standard once it's stable (or maybe at the same time as marking it stable).
Comment #30
xjmComment #31
xjmOh @BramDriesen you can also review the core governance to understand in more detail the different types of committers and what their responsibilities are. That said, it's also okay to not have a complete understanding, because issues can be RTBC with any of the committer signoff tags on them, and the committers know whose responsibilities are what and can fix the tags as needed.
Comment #32
bramdriesenNot sure if you've see it @xjm but #3401753: Add Announcements Feed to the Standard profile is the follow-up to add it to the standard profile. You did see the one for Unami 😉
Thanks as well for the link to the core governance and your guidance!
Comment #36
lauriiiThis seems fine for me to mark as stable so that we can enable it by default and start collecting feedback.
Committed 645d5de and pushed to 11.x. Also cherry-picked to 10.2.x. Thanks!
Comment #37
longwave