Uploaded image for project: 'Mongoid'
  1. Mongoid
  2. MONGOID-5450

Persistence context improvements

XMLWordPrintableJSON

    • Type: Icon: Epic Epic
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: Persistence
    • Labels:
      None
    • 5
    • 5
    • 6
    • 100
    • Hide

      Engineer(s): Neil Shweky

      2022-11-22: Updated target end date to 2022-12-09
      Status Update:

      • Focus has been on other Ruby and Driver work
      • No updates

      2022-11-11:

      Engineer: Neil Shweky

      Status Update:

      • Focus has been on other Ruby and Driver work
      • No updates

      Rationale for delays:

      • N/A

      Risks:

      • N/A

      2022-10-28: Setting Target Date to 2022-11-11

      Engineer: Neil Shweky

      Status Update:

      • Consolidated tickets under this epic for the original scope and any additional tickets that were spawned from completing that work
      • Two tickets backlogged for this epic, one currently in code review
      • Focus has been on other Mongoid and Driver work

      Rationale for delays:

      • Sorting out overlapping and conflicting customer feedback / requirements in some of the tickets

      Risks:

      • No risks

      2022-10-18: Setting Target Date to 2022-10-28

      Engineer: Neil Shweky

      Status Update:

      • Neil has completed this Epic's original scope
      • This Epic will be revisited when Neil is back from holiday
        • Remaining tickets that Oleg had created before leaving MongoDB will be moved to a new Epic and Backlogged til a later date
      • This Epic will complete within budget, no updates to cost

      Rationale for delays:

      • N/A

      Risks:

      • No risks

      2022-10-04: Setting Target Date to 2022-10-14

      Engineer: Neil Shweky

      Status Update:

      • Neil has completed this Epic's original scope
      • Oleg had a tech design up for review and is no longer with MongoDB
      • This Epic will be revisited next week and most likely be closed out as complete
        • Remaining tickets that Oleg had created will most likely be moved to a new Epic and Backlogged til a later date
      • This Epic should complete within budget

      Rationale for delays:

      • N/A

      Risks:

      • No risks

      2022-09-20: Setting target date to 2022-09-30

      Engineer: Neil Shweky

      Status Update:

      • Neil has completed this Epic's core implementation
      • Team is evaluating if it is feasible to include a Community request for a global persistence override as part of this epic
      • Review for Oleg's Tech Design Scheduled for 2022-09-27

      Rationale for delays:

      • N/A

      Risks:

      • No risks

      2022-09-07: Setting target date to 2022-09-16

      Engineer: Neil Shweky

      Status Update:

      • Neil has completed this Epic's core implementation
      • Team is evaluating if it is feasible to include a Community request for a global persistence override as part of this epic

      Rationale for delays:

      • N/A

      Risks:

      • No risks

      2022-08-23: Setting target date to 2022-09-06

      Engineer: Neil Shweky

      Status Update:

      • Neil has completed most of this Epic's implementation
      • There is one ticket remaining
        • Team plans to discuss the implementation specifics together once everyone is back from PTO

      Rationale for delays:

      • N/A, ahead of schedule

      Risks:

      • No risks
      Show
      Engineer(s): Neil Shweky 2022-11-22: Updated target end date to 2022-12-09 Status Update: Focus has been on other Ruby and Driver work No updates 2022-11-11: Engineer: Neil Shweky Status Update: Focus has been on other Ruby and Driver work No updates Rationale for delays: N/A Risks: N/A 2022-10-28: Setting Target Date to 2022-11-11 Engineer: Neil Shweky Status Update: Consolidated tickets under this epic for the original scope and any additional tickets that were spawned from completing that work Two tickets backlogged for this epic, one currently in code review Focus has been on other Mongoid and Driver work Rationale for delays: Sorting out overlapping and conflicting customer feedback / requirements in some of the tickets Risks: No risks 2022-10-18: Setting Target Date to 2022-10-28 Engineer: Neil Shweky Status Update: Neil has completed this Epic's original scope This Epic will be revisited when Neil is back from holiday Remaining tickets that Oleg had created before leaving MongoDB will be moved to a new Epic and Backlogged til a later date This Epic will complete within budget, no updates to cost Rationale for delays: N/A Risks: No risks 2022-10-04: Setting Target Date to 2022-10-14 Engineer: Neil Shweky Status Update: Neil has completed this Epic's original scope Oleg had a tech design up for review and is no longer with MongoDB This Epic will be revisited next week and most likely be closed out as complete Remaining tickets that Oleg had created will most likely be moved to a new Epic and Backlogged til a later date This Epic should complete within budget Rationale for delays: N/A Risks: No risks 2022-09-20: Setting target date to 2022-09-30 Engineer: Neil Shweky Status Update: Neil has completed this Epic's core implementation Team is evaluating if it is feasible to include a Community request for a global persistence override as part of this epic Review for Oleg's Tech Design Scheduled for 2022-09-27 Rationale for delays: N/A Risks: No risks 2022-09-07: Setting target date to 2022-09-16 Engineer: Neil Shweky Status Update: Neil has completed this Epic's core implementation Team is evaluating if it is feasible to include a Community request for a global persistence override as part of this epic Rationale for delays: N/A Risks: No risks 2022-08-23: Setting target date to 2022-09-06 Engineer: Neil Shweky Status Update: Neil has completed most of this Epic's implementation There is one ticket remaining Team plans to discuss the implementation specifics together once everyone is back from PTO Rationale for delays: N/A, ahead of schedule Risks: No risks

      Summary

      What is the problem or use case, what are we trying to achieve?

      Motivation

      Who is the affected end user?

      Who are the stakeholders?

      How does this affect the end user?

      Are they blocked? Are they annoyed? Are they confused?

      How likely is it that this problem or use case will occur?

      Main path? Edge case?

      If the problem does occur, what are the consequences and how severe are they?

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      Is this ticket required by a downstream team?

      Needed by e.g. Atlas, Shell, Compass?

      Is this ticket only for tests?

      Is this ticket have any functional impact, or is it just test improvements?

      Cast of Characters

      Engineering Lead:
      Document Author:
      POCers:
      Product Owner:
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel

      No scope or tech design is required for this epic.

            Assignee:
            dmitry.rybakov@mongodb.com Dmitry Rybakov
            Reporter:
            oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              16 weeks, 4 days