dev:meetings:2013-08-27
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
dev:meetings:2013-08-27 [2013/08/23 10:17] – 2.3.10 status update erickson | dev:meetings:2013-08-27 [2013/08/27 16:14] – lebbeous | ||
---|---|---|---|
Line 3: | Line 3: | ||
* 2:00:00 p.m. Tuesday, August 27, 2013 in Canada/ | * 2:00:00 p.m. Tuesday, August 27, 2013 in Canada/ | ||
* 18:00:00 Tuesday, August 27, 2013 in UTC | * 18:00:00 Tuesday, August 27, 2013 in UTC | ||
+ | |||
+ | ===== Minutes links ==== | ||
+ | * Minutes: [[http:// | ||
+ | * Minutes (text): [[http:// | ||
+ | * Log: [[http:// | ||
===== Action Items from Last Meeting ===== | ===== Action Items from Last Meeting ===== | ||
Line 8: | Line 13: | ||
* **Status: | * **Status: | ||
- berick and eeevil to cut 2.3.9 and 2.4.1 on 2013-07-17 | - berick and eeevil to cut 2.3.9 and 2.4.1 on 2013-07-17 | ||
- | * berick released 2.3.10 8/23 | + | * **Status:** both releases out the door |
- gmcharlt will talk to bshum about updating display of 2.2 on the downloads page | - gmcharlt will talk to bshum about updating display of 2.2 on the downloads page | ||
- | * **Status: | + | * **Status: |
==== GSoC reports ==== | ==== GSoC reports ==== | ||
+ | Our student seems to have disappeared again. | ||
==== Release info ==== | ==== Release info ==== | ||
Line 23: | Line 28: | ||
=== Evergreen === | === Evergreen === | ||
+ | |||
+ | * 2.3.10 released 8/23 | ||
+ | * 2.4.2 cut 8/23, release as soon as a second set of eyes pass over the tarball | ||
[placeholder] | [placeholder] | ||
+ | ==== QA Topics ==== | ||
+ | |||
+ | * Do we want to adopt/ | ||
+ | * Example tests: http:// | ||
+ | * Test generator script: http:// | ||
+ | |||
+ | ==== DB maintenance plan ==== | ||
+ | * Mike Rylander re-raises the proposal of carving the baseline SQL schema files in stone at major releases and using change-specific upgrade scripts to roll forward to a given, known-good state at minor version and revision upgrades. | ||
+ | * Reduced schema churn | ||
+ | * More people can take more time to understand the schema | ||
+ | * Make deprecate/ | ||
+ | * Realistically clear the way for an intelligent upgrade scripts that inspect config.upgrade_log and apply exactly what is needed | ||
+ | * Simpler change management | ||
+ | * Do things in one place, not two | ||
+ | * Committers have less to do AND to test | ||
+ | |||
+ | ==== Hack-A-Way 2013 plans ==== | ||
+ | |||
+ | * Question raised on whether there' | ||
+ | * Suggestion to create a wiki page similar to last year's Hack-A-Way with ideas (see [[dev: |
dev/meetings/2013-08-27.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1