Repository navigation
docs: record full release validation and remove stale references - #19
Merged
Merged
Conversation
Records the completed release-validation pass in Compatibility.md: the packed NuGet artifact (not a ProjectReference) was verified in a separate minimal host at both the minimum (30.11.0) and latest (31.8.4) Xperience versions, covering the admin UI, all three export formats with real row-content checks, and form cloning. Also notes the minimal-host gaps found along the way (AddAuthentication, UseStaticFiles/UseCookiePolicy, MapRoutes) and why DancingGoat itself can't be used for minimum-version testing (its bundled commerce samples require a newer Xperience version). Flips the Export and Removal specs' status lines from "prerelease validation in progress" to "implemented and validated" now that the above is genuinely complete, and points them at the new validation history instead of a generic checklist reference. Removes references to the never-built "proposed Retention" feature from the removal spec, which had leaked into several sections (shared deletion engine, security, performance, test strategy, acceptance criteria) as if a sibling specification existed. Replaces the scattered mentions with a single, explicit "Out of scope" entry noting retention was considered and deferred, and drops the dangling reference to a form-submission-retention.md file that was never created. Updates Release-Process.md's stale "next planned release" pointer from the already-shipped beta.4 to beta.5.
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
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
docs/Compatibility.md: the packed NuGet artifact (not aProjectReference) was verified in a separate minimal host at both the minimum (30.11.0) and latest (31.8.4) Xperience versions — admin UI, all three export formats with real row-content checks, and form cloning all confirmed at both boundaries. Also documents the minimal-host gaps found along the way (AddAuthentication,UseStaticFiles/UseCookiePolicy,MapRoutes) and why DancingGoat itself can't serve as the minimum-version test bed (its bundled commerce samples require a newer Xperience version, unrelated to this toolkit).form-submission-retention.mdfile that was never created.Release-Process.md's stale "next planned release" pointer from the already-shippedbeta.4tobeta.5.Test plan
30.11.0and31.8.4, admin UI, CSV/Excel/XML exports, form cloning) directly before writing this summary.