dev:meetings:2009-10
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:2009-10 [2009/10/13 10:27] – added note about craftsman erickson | dev:meetings:2009-10 [2009/10/16 17:14] – add link to minutes wlayton | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== IRC developer meeting for October 2009 ====== | ====== IRC developer meeting for October 2009 ====== | ||
- | Please add agenda items here: | + | See also: [[: |
+ | |||
+ | **Agenda:** | ||
* 1.6 release status | * 1.6 release status | ||
Line 10: | Line 12: | ||
* Importing MFHD monographic holdings records separate from bibliographic records | * Importing MFHD monographic holdings records separate from bibliographic records | ||
* Invalid date of birth: [[http:// | * Invalid date of birth: [[http:// | ||
+ | * Conify (particularly Hours of Operation and Addresses) - [[http:// | ||
* others ... ? | * others ... ? | ||
* Aside: we should post a response to a bug posted on the mailing list if the reported bug is fixed, even if we also enter that bug in the bug tracker; with a link to the pertinent commit + bug | * Aside: we should post a response to a bug posted on the mailing list if the reported bug is fixed, even if we also enter that bug in the bug tracker; with a link to the pertinent commit + bug | ||
Line 20: | Line 23: | ||
* Lowering the barriers to participation | * Lowering the barriers to participation | ||
* There haven' | * There haven' | ||
+ | |||
+ | * Bug tracking and QA | ||
+ | * Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness? | ||
+ | * Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad | ||
* Release process | * Release process | ||
Line 26: | Line 33: | ||
* Devs can do DVCS model today on their own branches, but would be nice to have a single repo that holds all of the branches - or perhaps at least a list of all the different locations that branches are hosted (github, launchpad, google code) | * Devs can do DVCS model today on their own branches, but would be nice to have a single repo that holds all of the branches - or perhaps at least a list of all the different locations that branches are hosted (github, launchpad, google code) | ||
- | * Bug tracking and QA | + | * Acquisitions (based on the survey, |
- | * Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness? | + | |
- | * Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad | + | * oils_i18n_gettext, and all those untranslated things inserted into tables in 950.data.seed-values.sql without the pinned primary key values that oils_i18n_gettext needs |
* Future development | * Future development | ||
* What's shaking in the near future? | * What's shaking in the near future? | ||
* Any long term projects that we need to start laying the groundwork for now? | * Any long term projects that we need to start laying the groundwork for now? | ||
+ | * Telephony | ||
* Status of Craftsman and continued support/ | * Status of Craftsman and continued support/ | ||
| | ||
* Monthly IRC Development meetings (re: Grace' | * Monthly IRC Development meetings (re: Grace' | ||
* roles | * roles |
dev/meetings/2009-10.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1