chore: remove textual roadmap in favor for Starmap #2036
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MarcoPolo
approved these changes
Jan 31, 2023
|
Thanks for referencing the starmap issue.. this helps us to know how important the list feature is. I've bumped up it's priority a bit.. and I think it can be done outside of the d3 refactor (pln-planning-tools/Starmap#237), which should help for getting the list feature done sooner than later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The textual roadmap is a chore to maintain and update. The PL organization is using Starmap, I propose we rely on Starmap to display the timeline instead of maintaining it in a markdown file.
Furthermore, when this Starmap feature pln-planning-tools/Starmap#120 is shipped, we can leverage that to have a textual view