Versions Compared

Old Version 8

changes.mady.by.user Khalilah Gambrell

Saved on

compared with

New Version 9

changes.mady.by.user Khalilah Gambrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  

...

 Topics

Time

Presenter

Agenda/Notes

Announcements (feel free to update Agenda/notes)10 minutes All 

Questions:  Expectations for POs that have no ECS requirements - If you have time to do exploratory testing then do so. 

AWS costs10 minutesPeter Murray 

AWS Costs Review Group Home

> Effective with "Q" release development 

> Ideally the approval process should take a week so account for it when making a request to Kitfox for UAT, etc. 

> Question 1: Has this been communicated to the dev teams/scrum masters, or do we need to take this back to the various dev teams? Group has met with Dev leads. 

> Question 2: Is there a list of the existing environments/which team it belongs to/what the lifespan of the env is? This process will generate this list. 

>Question 3: Is it possible to push request to Kitfox queue? Possibly.  AWS cost team needs to discuss with Yogesh

Review "Q" release timeline15 minutes

Oleksii Petrenko

Quesnelia (R1 2024) release plan
Duration: 11 sprints long (mid Sprint 176 - mod Sprint 187) - 10.5 development sprints + 0.5 sprint for modules releases
Crucial milestones:
16 Feb 2024 - Ramsons R2 2024 release scope composition deadline
01 Mar 2024 - Deadline for acceptance of new modules by Technical Council at Poppy (R1 2024)
01 Mar 2024 - OKAPI, RMB, Stripes, SpringWay freeze
01 Mar 2024 - Quesnelia Features test case preparation deadline
11 Mar 2024 - Ramsons R2 2024 release scope refinement deadline
15 Mar 2024 - Modules feature development code freeze
22 Mar 2024 - Module release deadline
01 Apr 2024 - 19 Apr 2024 - Quesnelia R1 2024 Release testing and hardening period
29 Apr 2024 - Release is public

Review list of proposed topicsRemaining time AllProposed PO topics for the next two meetings

...