[GODRIVER-488] Godriver MongoDB 4.2 Support Created: 11/Jul/18 Updated: 23/Oct/19 Resolved: 15/Aug/19 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Rathi Gnanasekaran | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | driver-current-quarter | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Start date: | |
| End date: | |
| Calendar Time: | 10 weeks |
| Detailed Project Statuses: | 2019-06-24: initial target of 2019-08-19 (8 weeks) 2019-07-08: updated target of 2019-09-02 (10 weeks)
|
| Comments |
| Comment by Ian Whalen (Inactive) [ 09/Jul/19 ] |
|
setting start date and adjusting end date to a 2 week increment. |
| Comment by Esha Bhargava [ 01/Jul/19 ] |
|
ian.whalen That was my bad. Kris had given me a target date of 08/09 which is why the end date is 08/12. The meta data did not reflect the right info. I have updated it. |
| Comment by Ian Whalen (Inactive) [ 28/Jun/19 ] |
|
Hmmm, apologies for the misunderstanding then - regardless of what was discussed offline, we explicitly agreed to defer it until after 4.2 support wrapped and indicated that by putting it in an epic ranked below 617. |
| Comment by Kristofer Brandow (Inactive) [ 28/Jun/19 ] |
|
ian.whalen, it's a ticket that Jeff and I had talked about pulling in and that he really wanted to get done on the tail end of |
| Comment by Ian Whalen (Inactive) [ 28/Jun/19 ] |
|
esha.bhargava it looks like the end date here is August 12th but the planning metadata says July 8th. Can you help me understand the real target end date? It also looks like kris.brandow you're working on 'codegen everything' ahead of 4.2 support being complete. We explicitly deferred that work. What changed? |