dev:meetings:2014-02-12
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:meetings:2014-02-12 [2014/02/11 14:02] – [New Business] bshum | dev:meetings:2014-02-12 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 4: | Line 4: | ||
* 2:00:00 p.m. Wednesday, February 12, 2014 in Canada/ | * 2:00:00 p.m. Wednesday, February 12, 2014 in Canada/ | ||
* 19:00:00 Wednesday, February 12, 2014 in UTC | * 19:00:00 Wednesday, February 12, 2014 in UTC | ||
+ | |||
+ | =====Minutes===== | ||
+ | * Minutes: | ||
+ | * Minutes (text): [[http:// | ||
+ | * Log: [[http:// | ||
===== Action Items from Last Meeting ===== | ===== Action Items from Last Meeting ===== | ||
* bshum to summarize bug tracking based on feedback from developers | * bshum to summarize bug tracking based on feedback from developers | ||
+ | * **Status**: Deferring, will do this at the conference if we run out of time | ||
* gmcharlt to cut OpenSRF 2.3-beta next week | * gmcharlt to cut OpenSRF 2.3-beta next week | ||
+ | * **Status**: ? | ||
* eeevil to publish detailed plan about freezing baseline schemas between EG releases and using deprecates/ | * eeevil to publish detailed plan about freezing baseline schemas between EG releases and using deprecates/ | ||
+ | * **Status**: ? | ||
* dbwells to review bug 1242999 | * dbwells to review bug 1242999 | ||
+ | * **Status**: Reviewed and committed to master, will backport for 2.5.3. | ||
* 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" | ||
* dbs will write up the release notes as promises in bug # 1261939 for per-library TPAC pages | * dbs will write up the release notes as promises in bug # 1261939 for per-library TPAC pages | ||
+ | * **Status**: Done via http:// | ||
* bshum to set new calendar entries for 2.6 milestone events and give access to dbwells to dev calendar. | * bshum to set new calendar entries for 2.6 milestone events and give access to dbwells to dev calendar. | ||
+ | * **Status**: Gave dbwells access to dev calendar, did not add milestone events yet. | ||
* bill to open opensrf LP websocket ticket with current info | * bill to open opensrf LP websocket ticket with current info | ||
+ | * **Status**: Ticket opened : https:// | ||
===== Updates ===== | ===== Updates ===== | ||
- | ==== GSoC reports | + | ==== GSoC ==== |
- | [placeholder] | + | Deadline for GSoC organization applications is February 14, 2014. Are we going to apply this year? (Better question: do we have willing and able mentors this year? |
==== Release info ==== | ==== Release info ==== | ||
Line 34: | Line 47: | ||
===== 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