Problem/Motivation
According to #3027054-100: Help Topics module roadmap: the path to beta and stable there are no blockers left to mark Help Topics as stable, and to start merging it into the core Help module.
- Last actionable item is #3037230: Finalize the merge of Help Topics into Help
Proposed resolution
- Remove "Experimental" status from Help Topics and mark it as stable core module.
Remaining tasks
- Swap Core (Experimental) for Core in the info file
- Check @internal in php-docs to allow move parts into help module
- Finalize scope of #3037230: Finalize the merge of Help Topics into Help
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 3355659-7.patch | 4.08 KB | andypost |
| #7 | interdiff.txt | 2.83 KB | andypost |
Comments
Comment #2
andypostComment #3
andypostLet's see how tests will run
Comment #4
andypostAnd one more fix
Comment #5
andypostComment #6
andypostand stable is not needed
Comment #7
andypostComment #8
amber himes matzUpdated issue summary and title for clarity.
Comment #9
catch#3037230: Finalize the merge of Help Topics into Help suggests that rather than actually mark help topics as stable, we would instead move the code from help topics into the existing help module. With that the existing help_topics module would need to be marked obsolete and eventually removed from core and we just have 'help' with both help topics and hook_help(), and then eventually deprecate hook_help().
I think we definitely don't want two help modules in core, so we either need to merge help topics into help, or change the plan to make help topics the only module in core by deprecating and removing help - however doing so would mean two stable help modules in core until that happens, and 'help' still seems like a good namespace to keep in core, so for me the original plan is better.
So... I think we should mark this as a duplicate of #3037230: Finalize the merge of Help Topics into Help and focus efforts over there instead, but leaving needs work for discussion.
Comment #10
andypostMy intent to make it stable is just to find better wording for class-comments, OTOH on the move we probably should spread topics to their modules (it was separate issue) because help (as stable) can't show topics from help_topics (experimental)
So this issue is an attempt to solve chicken-egg loop
This comment is all over classes, when moving to help module no BC required but wording needs some better wording
Comment #11
catchIf we move the help topics API to help module, that would count as stable, then the individual help topics can all move to their respective modules. Or we could just decide to do both at the same time if there's a proper chicken and egg situation.
Although I think it would be possible for help topics module to continue providing the topics for other core modules while that's happening (especially if we get it all done within 8.2's development cycle for example).
Comment #12
andypostThank you @catch! Then next actionable issue is #3087499: Merge Help Topics classes into Help with BC layer
I still hope it will be just a move of classes with BC phantoms in help topics, then update hook to disable help-topics
I will start in this weekend
Comment #13
andypostSetting proper status