Differences

This shows you the differences between two versions of the page.

--- dev:meetings:2010-12-21 [2010/12/21 11:39] – Knocking off an action item dbs
+++ dev:meetings:2010-12-21 [2010/12/22 11:08] – formatting - stupid syntax highlighting dbs
@@ Line 30: / Line 30: @@
         * Status: Done - here's [[:dev:evergreen:supported_releases|the page]], please provide feedback to the [[http://markmail.org/message/z5dprw6ugkozghi5|open-ils-general mailing list]]
       - Write release notes for OpenSRF 1.6.<del>1</del>2
+        * **ACTION**: Deferred with an offer to adopt out to a loving family
       - Implement proper [[http://sourceware.org/autobook/autobook/autobook_91.html|library versioning using autotools]] for Evergreen release.
+        * **ACTION**: Deferred with an offer to adopt out to a loving family
     - Bug-squashing related:
       * **ACTION**: Jason Stephenson (head bug wrangler) to go through the list of "Fix Committed" bugs and change those that were tied to beta5 release to "Fix Released"
@@ Line 37: / Line 39: @@
         * Status: Done
     - **ACTION**: Mike Rylander to write release notes for Evergreen 1.6.1.4 (5?)
+        * **STATUS**: Deferred with an offer to adopt out to a loving family
     - **ACTION**: Jason Etheridge to update acq.open-ils.org with RC1 to allow for more public testing.
+        * **STATUS**: Deferred until 2.0-RC1 actually exists.
   - General news and issues:
     * OpenSRF 1.6.2 was released on Sunday
+      * **NOTES**:
+        * dbs noted that OpenSRF 1.6.2 is recommended for EG 1.6.1+
+        * dbs noted that removal of ''/openils/lib/*oils*'' was required for a successful recompile of EG after upgrading from OpenSRF 1.2 to 1.6 (a [[http://paste.lisp.org/+2IXC|full log of the upgrade process]] is available, warts and all
     * There is now an [[https://launchpad.net/~evergreen-security|Evergreen security team]] on LaunchPad
       * This team is currently composed of the [[:contributing:contributors|current committers]], significant code contributors, and security bug reporters; their only power at the moment is to be able to read and edit LaunchPad bugs marked as "Security" issues
+        * **ACTION**: miker suggested: an "anyone can post" moderated list made up of the LP sec team members; if yes, ESI can host.  miker will propose on the -dev list
+          * **STATUS**: Email sent to -dev.
       * There is some desire for a secure channel for discussions (mailing list, secured XMPP server, ?) outside of bugs - talking about security vulnerabilities on IRC is not ideal - but no action as of yet
       * LaunchPad mailing lists are all public, so that's not an option
     * OpenLibrary added content - there was a request on the list to backport to 1.6; should just be a matter of copying OpenLibrary.pm into place but per release guidelines new features should go into a new release (1.6.3.0)
+      * **ACTION**: Consensus vote was "too late for 1.6"; will not be backported.  Suggestion of a ILS-Contrib backport was raised.
     * Maybe we need a release checklist to follow so that steps for a release don't slip through the cracks (e.g. 1.6.1.5 was cut and uploaded on 2010-12-10 but not updated on downloads page until 2010-12-21 and has not been announced on the mailing list or blog)? Something like the following, perhaps where a given branch has one person to fulfill each responsibility, and each of these steps could be further documented on the wiki (for example, [[:dev:rolling_a_release|rolling an OpenSRF release]] so that we can build more resilience into our release and development processes:
       - //release-lead// cuts the release tarball and uploads to evergreen-ils.org
@@ Line 54: / Line 64: @@
       - //web-team-member// updates download page with new release
       - //communication-team-member// announces release on mailing list / blog and updates wikipedia / freshmeat
+      * **ACTION**: Consensus vote was to adopt this checklist.  miker will propose a release coordination mailing list on -dev and -general;  should be called out in the community meeting for non-developer resource acquisition (release-notes-writer, web-team-member and communication-team-member, in the least)
   - 1.6.1.x release status (current release = 1.6.1.5)
     * http://evergreen-ils.org/downloads.php needs to reflect this, still says 1.6.1.4
@@ Line 59: / Line 70: @@
   - 1.6.2.x release status (current release = 1.6.2.0-rc1)
     - Any feedback on 1.6.2.0-rc1?
+      * **NOTES**: No external feedback.  1.6.2.0 will be cut with 2.0-RC1 (see below)
   - 2.0 release status
     * Bugs targeted to [[https://launchpad.net/evergreen/+milestone/2.0rc1|RC1]]
+      * **ACTION**: [[https://bugs.launchpad.net/evergreen/+bug/688015|Merging authority records does not change the attached bibliographic record(s) name]] looks like the only blocker.  Fix discussed, amounting to firing the updater against bibs that were previously attached to the subordinate authority.
     * [[https://bugs.launchpad.net/evergreen/+bugs?orderby=-datecreated|Most recently reported bugs]]
       * Maybe a review of recently reported bugs should fall under a general QA/bug wrangler section?
     * A beta5 virtual image is available for download, just in time for...
     * 2.0 RC1?
+      * **ACTION**: 2.0-RC1 to be cut once "Merging authority records" bug (above) is addressed, and Dan Wells has a chance to commit Serials fixes.
   - Post-2.0 planning (probably not time to discuss today, but we should start thinking about things like this):
     * Update Dojo from 1.3 (released March 2009) to 1.5 (out since July 2010)?
     * Move to git or some other DVCS for the official repository?
+      * **ACTION**: discussion postponed until next meeting.
   - (2 min) Schedule next meeting
-    * [[dev:meetings:2010-12-21|Tuesday, December 28th]] at 12:00 EST, 9:00 PST
       * Guessing not... January 4th? January 11th?
+      * **ACTION**: January 4th is the date of consensus
+      * [[dev:meetings:2011-01-04|Tuesday, January 4th]] at 12:00 EST, 9:00 PST
     * http://evergreen-ils.org/calendar has the next 6 weeks blocked for the same time, same place