dev:meetings:2014-02-12
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:meetings:2014-02-12 [2014/02/12 11:30] – [GSoC reports] dbs | dev:meetings:2014-02-12 [2014/02/12 13:51] – [Action Items from Last Meeting] dbw2 | ||
---|---|---|---|
Line 14: | Line 14: | ||
* **Status**: ? | * **Status**: ? | ||
* dbwells to review bug 1242999 | * dbwells to review bug 1242999 | ||
- | * **Status**: | + | * **Status**: |
* bshum to fix up the 2.4.5 and set 2.4.6 milestones in LP | * bshum to fix up the 2.4.5 and set 2.4.6 milestones in LP | ||
* **Status**: Done, though I need to go through and update the bug statuses to "fix released" | * **Status**: Done, though I need to go through and update the bug statuses to "fix released" | ||
Line 42: | Line 42: | ||
===== New Business ===== | ===== New Business ===== | ||
+ | - PostgreSQL 9.3 support | ||
+ | * There are several aspects of PostgreSQL 9.3 that break Evergreen: | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * Stricter type handling in function arguments (INTs no longer automatically coerced to TEXTs) breaks STRING_AGG() in a few places, possibly other functions - not sure this is bugged yet | ||
+ | * https:// | ||
+ | * Should we make PostgreSQL 9.3 support a release blocker for Evergreen 2.6 to avoid accumulating too much technical deficit / causing too much pain for those who aren't aware of the 9.3 problems? | ||
+ | * And obviously we need pgTAP tests to ensure that we get the expected behaviour from 9.1 through 9.3 (and beyond) | ||
- Evergreen Hackfest Plans | - Evergreen Hackfest Plans | ||
- | | + | |
- | | + | |
dev/meetings/2014-02-12.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1