Add roadmap and upstream backlog triage - #56
Open
davestewart wants to merge 2 commits into
Open
Conversation
Sets out the planned release sequence, from the v1.2.1 housekeeping patch through to the v2.0.0 module system overhaul, and records the triage of issues #5 and #14 against the current source. Every upstream PR listed in #5, and every change on the upstream 0.5.10 branch, has been checked against current source and assigned to a release, recommended as won't-fix, or flagged as needing a redesigned fix. Co-Authored-By: Claude <noreply@anthropic.com>
Records what each release needs from the spectre-docs repo, and how the docs site is wired up: the sidebar is generated from folder structure and frontmatter, so most new pages need no config change, but the JS badge list is hard-coded and dark mode is currently disabled outright. Also notes that the flat source paths #48 changes are a documented public API, and sets out the forwarding-shim option that would let the folder move happen without breaking them. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds
ROADMAP.md, setting out the planned release sequence and recording the triage of the outstanding upstream backlog.Release sequence
The principle is to ship every non-breaking improvement first, then bundle everything already known to be breaking into a single major release, so users absorb the upgrade cost once.
@use/@forwardmigration, grouped imports, deferred normalize rules, colour custom properties, spacing review (Move files to folders #48, @use and @forward #54, Simplify partial imports #29, Review padding and margins across framework #4 + PRs Upgrade normalizations #45, Move files to folders #49, Add CSS variables for color #38)Colour is split out of #19 deliberately: PR #38's author flags native colour maths as differing subtly from Sass, which makes it a major-version change. The non-colour half has no such problem and can ship early.
Within v2.0.0 the order matters — #49 (folder move) must land before #54 (module migration), since the migration rewrites every relative import path and doing it first means writing them twice.
Backlog triage
#5 and #14 are lists of unreviewed upstream work rather than changes in themselves. Every item has been checked against current source:
.lesspatch against a Sass-only codebase, and the pre-fork@useattempt (too stale to merge, but useful reference for @use and @forward #54)spectre-docsbacklog.show-*bug but its fix just moves the breakage from flex content onto block contentNone of the upstream
0.5.10branch has been merged. Notes are included on cleaning up the column ordering utilities during the port — dropping IE prefixes, adding a missing!default, and removing rules redundantly re-emitted in every breakpoint.Closes #5
Closes #14
🤖 Generated with Claude Code