dev:meetings:2013-03-12
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dev:meetings:2013-03-12 [2013/03/11 23:07] – bshum | dev:meetings:2013-03-12 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * 18:00:00 Tuesday, March 12, 2013 in UTC | * 18:00:00 Tuesday, March 12, 2013 in UTC | ||
| + | ===== Logs and minutes ===== | ||
| + | |||
| + | * Minutes: | ||
| + | * Minutes (text): http:// | ||
| + | * Log: http:// | ||
| ===== Action Items from Last Meeting ===== | ===== Action Items from Last Meeting ===== | ||
| Line 15: | Line 20: | ||
| * **STATUS**: [[http:// | * **STATUS**: [[http:// | ||
| - gmcharlt to do some branch management with an eye towards an OpenSRF 2.2 release in the next few weeks | - gmcharlt to do some branch management with an eye towards an OpenSRF 2.2 release in the next few weeks | ||
| - | * **STATUS** | + | * **STATUS** |
| ==== GSoC ==== | ==== GSoC ==== | ||
| Line 28: | Line 33: | ||
| === Evergreen === | === Evergreen === | ||
| - | * 2.4 release: | + | * 2.4 release: |
| - | * yaz - currently installing 4.2.32; current source version is 4.2.51 | + | * Let's revisit all of the dependencies that we currently install from source for newer versions or for ditching, including: |
| - | * Net:: | + | * yaz - currently installing 4.2.32; current source version is 4.2.51 |
| - | * SpiderMonkey and libjs - who cares about the versions, but should we officially deprecate script-based circ as of 2.4? | + | * Net:: |
| - | * libdbi / libdbi-drivers - only installed from source on Debian Squeeze and Ubuntu Lucid | + | * SpiderMonkey and libjs - who cares about the versions, but should we officially deprecate script-based circ as of 2.4? |
| - | * XULRunner - let's look at merging https:// | + | * libdbi / libdbi-drivers - only installed from source on Debian Squeeze and Ubuntu Lucid |
| + | * XULRunner - let's look at merging https:// | ||
| + | * **Q**: Would it be worth turning this into a documented, repeatable release process that ultimately the release manager signs off on (although naturally anyone else could do the actual work & provide assessments / suggestions). | ||
| + | * Proposed addition to release manager processes: No release tarball shall be released unless at least one person has gone through a clean install and confirmed that it actually works. | ||
| + | * Proposed addition to release manager processes: Clearly articulate (in the release notes?) which operating systems and browsers (and versions & bitness of each) are supported by a given release. Not just Linux distros, which should have one or more distro champions; but also Windows (to answer anticipated questions like: "Is the staff client supported on Windows 8 64-bit?" | ||
| ==== Software Performance Evaluation ==== | ==== Software Performance Evaluation ==== | ||
| + | * MassLNC has started the process of creating [[dev: | ||
| + | * We would like to involve the community in selecting a consultant(s). Is anyone willing to volunteer to work with us on this? | ||
dev/meetings/2013-03-12.1363057675.txt.gz · Last modified: 2022/02/10 13:34 (external edit)