Slice 16 — Phase 2B close-out + v1.2.0 - #15
Merged
Conversation
Phase 2B delivered Viewport 2.0 visualization (Slice 13 Path B), HM-1 per-center viridis coloring (Slice 14), HM-2 prediction-field grid + X-Ray (Slice 15), and a drag-drop installer (PR #12 with two follow-ups). No Phase 1 or Slice 10A/11/12 touches; Phase 2A invariants preserved throughout. Top-level CMakeLists.txt project VERSION bumps to 1.2.0. maya_node/CMakeLists.txt RBFMAX_MAYA_PLUGIN_VERSION follows; this value is injected into plugin_info.hpp via configure_file and bound into the .mll via MFnPlugin::registerNode's 4th-arg version string. Verified via mayapy: cmds.pluginInfo('rbfmax_maya', q=True, version=True) returns '1.2.0' on both Maya 2022 and 2025 builds.
~145 LOC Slice 16 entry covering Phase 2B scope summary (5 PRs merged), quantitative summary (LOC / tests / F-stops), invariant tracking (Phase 1 / mRBFNode compute / mRBFShape R-44 / Slice 13 override config / Slice 14 viridis LUT — all zero-touch across the phase), tech-debt status table (T-17/R-45 resolved within Phase 2B; T-10/T-16/T-18/T-19/T-20 + dev_unload.py rolled to Phase 2C), Phase 2B reviewer-discipline summary (Rules 3/4 exercised + Rule 5 formalization from Slice 13), Phase 2C entry conditions (4 specific deliverables), Slice 16-specific validation (139/180/8 smokes/version injection assertion), post-merge tag plan (v1.1.0 retro on d624c79 + v1.2.0 on the merge commit). Also bumps README.md version badge to 1.2.0 (release link reference).
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
2 participants
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.
Summary
Phase 2B close-out. Pure retrospective + version bump. Zero functional code changes; zero test changes; zero installer changes.
project(rbfmax VERSION …)1.1.0 → 1.2.0RBFMAX_MAYA_PLUGIN_VERSION1.1.0 → 1.2.0 (injected intoplugin_info.hppvia configure_file)[1.2.0]CHANGELOG entry summarizing Phase 2B featuresPhase 2B at a glance
Test count: 163 → 180 (+17, 0 regressions). F-stops #5-#9 all resolved. Tech-debt: T-17 + R-45 resolved within phase; T-10 / T-16 / T-18 / T-19 / T-20 +
dev_unload.pyrolled to Phase 2C.Validation
buildPhase 1 ctest (clean reconfigure)build-adapterctestcmds.pluginInfo('rbfmax_maya', q=True, version=True) == '1.2.0'✅ on both Maya 2022 and 2025.mllsizes unchanged from Slice 15 (528,384 / 529,408) —"1.2.0"and"1.1.0"are same length so no section re-alignment.Post-merge — tag push
Two annotated tags to be pushed separately after merge (per Slice 12 DEVLOG's "tag deferred to Phase 2B end" promise):
Constraints respected
Test plan
pluginInfoversion returns'1.2.0'on both Maya 2022 and 2025