List view
Our scope of issues for CMS6
Due by April 16, 2025- Due by March 31, 2024
Changes targeted to the 5.1.0 release
Due by October 17, 2023- Due by January 30, 2023
Sprint goals: - Complete Google spikes - Frontend components are scaffolded and built for the session manager ? Unblock LinkField work by implementing the form schema
Due by March 1, 2021Sprint goals - Resolve notable regressions - Tag CWP 2.7.1-rc1 - Continue work on Session and LinkField initiatives
Due by February 15, 2021•1/1 issues closedSprint goals (split within squad) PHP 8 - Have PHP 8 CI builds passing in all CMS4 support modules Streamline MFA - Finalise and publish device management UI designs - Have a clear understanding of the compatibility, quality of code, and performance of the Session Manager module LinkField: - Finalise the remaining architectural decisions so that development can continue in the following sprint
Due by February 1, 2021Sprint Goals (Split between the Squad): LinkField: - Have underlying architecture decisions decided upon and implemented - Finalise outstanding issues relying on the above - Work with PUX to outline outstanding UX questions Streamline MFA - Investigate solutions for selected opportunities - Validate solutions with audience - Prepare remaining issues and work plan
Due by December 7, 2020Sprint Goals: - Resolve priority regressions identified in beta testing - Prepare and publish release candidates for: - CMS 4.7.0-rc1 - CWP 4.7.0-rc1 - Close out TravisCI shared config pull requests
Due by November 23, 2020Sprint goals: - Tag CMS beta - Complete regression testing of upcoming releases, including: - CMS 4.7.0 beta - CWP 2.x branch
Due by November 9, 2020Sprint goals - Focus on work required prior to 4.7 beta tag/ feature freeze
Due by October 26, 2020Sprint goals: - Dependancy upgrades are prepared in advance of beta tag (in ~4 weeks) - Used on table enhancement is merged
Due by October 12, 2020Sprint goals: - Kick off initiative to 'treat Bespoke like our customers' - Experience debt issues
Due by September 28, 2020Sprint goals: Things that _need_ to happen: - Release CWP 2.6.1 - Close out peer review of GraphQL work - Technical product demo
Due by September 15, 2020Sprint Goals: - Regression test 2.6.1-rc1 - Complete work from previous sprint - Kick off GraphQL v4 review Stretch Goals: - Early investigation of next sprint's work, highlights: - Cloud Build (finalise) - [Used on Table enhancements](https://github.com/silverstripe/silverstripe-asset-admin/issues/903) - [Queued jobs features](https://github.com/symbiote/silverstripe-queuedjobs/pull/290) - [SilverStripe 3.x to 4.5.x migration toolkit for at least medium sized projects](https://github.com/silverstripe/silverstripe-assets/pull/397)
Due by September 2, 2020* Addressing high impact bugs and issues
Due by August 18, 2020Sprint goal: - Have both the CWP and Bambusa demo run the latest stable version - Focus on high impact bug fixes from the Ready column
Due by August 4, 2020Sprint goal: - Publish the quarterly releases (4.6, CWP 2.6) - Publish the security releases (4.4.x, 4.5.x) - Publish the security releases (3.7.x, CWP 1.9.x)
Due by July 21, 2020•1/1 issues closedSprint goal: - Ensure we are in a good position to tag a stable release in the following sprint for 4.6; and - Be ready to release all new security patches Stretch goal: Address actions raised from the release retro.
Due by July 7, 2020Sprint goal: - Prepare quarterly release candidate, including calling out what we should aim to be in the tag, including: - Complete Solr/ fulltextsearch issues that are in peer review - Tag the release candidate, send to Insomnia for auditing
Due by June 23, 2020Sprint Goals: - Complete secure forms work carried from past sprint - Complete regression testing of beta/ dev recipe
Due by June 9, 2020Sprint goals: - Complete in-progress harden forms - Ensure all open security issues are ready for release - Stretch goal: complete search work
Due by May 26, 2020Sprint goals: - Complete development and design on secure forms initiative - Progress with security issues
Due by May 12, 2020- Due by April 28, 2020
- Due by March 16, 2020
Sprint goals: - Release hotfix for CVE-2020-9820 and CVE-2019-12245
Due by March 30, 2020Sprint goal: - This sprint will be a success if we have 'real' test environments defined and ready for testing - We have the bugs resolved and all of the required tasks created, ready for testing.
Due by March 16, 2020SPRINT GOALS: * Prepare enough work for a new core patch release (GraphQL fix, PHP 7.4 support) * Begin Dev and QA tooling epic
Due by March 2, 2020SPRINT GOAL: * Successfully release a patch version of core recipes and a release candidate of CWP * The release is conducted by those more new to the process to enhance their knowledge * Stetch goal: The improve developer tooling and QA epic begins
Due by February 17, 2020Getting ready for beta 4.6
Due by February 3, 2020SPRINT GOAL - Complete issues important to include in the upcoming release - Priority issues are: patching security vulnerabilities and fixing regressions from the 4.5 release
Due by February 3, 2020SPRINT GOALs - Complete outstanding in-progress issues from 2019 - Close out the 'stabilise the release process' epic
Due by January 20, 2020- Due by December 9, 2019
- Due by November 25, 2019
- Due by November 11, 2019
- Due by October 28, 2019
- Due by October 14, 2019
- Due by September 29, 2019
- Due by September 17, 2019
- Due by July 23, 2019
- Due by July 9, 2019•13/13 issues closed
- Due by June 25, 2019•15/15 issues closed
- Due by June 11, 2019•6/6 issues closed
- Due by May 28, 2019•4/4 issues closed
- Due by April 16, 2019•7/7 issues closed
- Due by April 1, 2019•5/5 issues closed
- Due by March 18, 2019•6/6 issues closed
- Due by March 4, 2019•2/2 issues closed