Differences

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

--- minutes_20110419 [2011/04/19 14:39] – demiankatz
+++ developers_call:minutes20110419 [2015/12/09 12:13] (current) – ↷ Page moved and renamed from minutes_20110419 to developers_call:minutes20110419 andre_l
@@ Line 11: / Line 11: @@
 The VuDL project is going to share VuFind's JIRA (see [[http://vufind.org/jira/browse/VUDL|here]]).  Please let Demian know if this causes problems for anyone.
@@ Line 19: / Line 20: @@
 A new version of the PHP Sonar plug-in has been released (0.4).  Demian has upgraded the [[http://vufind.org/sonar|VuFind Sonar server]].  The most visible improvement is a fix for a bug in duplicate code detection which was causing contents of the Smarty "compile" directory to show up (though the old bug has been replaced by a new bug, so the problem isn't really solved -- see [[http://jira.codehaus.org/browse/SONARPLUGINS-1093|SONARPLUGINS-1093]]).
+Preetha has made further progress on building tests of the record module.  Some people expressed interest in trying to run the tests so we can discuss them in more detail on future calls.
 ==== 3. New/Updated JIRA Tickets ====
@@ Line 53: / Line 54: @@
 Demian has set up a new branch for experimenting with Solr 3.1 ([[https://vufind.svn.sourceforge.net/svnroot/vufind/branches/solr3/]]), but no changes have been committed there yet.  Once an error-free configuration exists, it will be made available there for testing before getting pushed into the trunk.
 ==== 8. Next release: 1.1.1 vs. 1.2? ====
-In the first month after the release of VuFind 1.1, there haven't really been any bugs serious enough to justify a 1.1.1 release (unless you count the SolrMarc Dewey indexing problems, which affect a fairly narrow group of users).  We discussed whether we want to continue targeting a 1.1.1 release, or whether it makes more sense to jump directly to a 1.2 release with more drastic changes (i.e. Solr 3.1, expanded ILS driver functionality, etc.).
+Since VuFind 2.0 is still a fairly long way off (Summer, 2012 is the current target date for a beta), we need to plan our strategy for the next release.
+Important note on release numbering: Demian's view is that subsetting a minor release indicates bug fixes that do not require a new upgrade script...  while a full minor release indicates significant changes that require an upgrade.  That is to say, for upgrade purposes, 1.0 and 1.0.1 are equivalent, but 1.0 and 1.1 are not.
+In the first month after the release of VuFind 1.1, there haven't really been any bugs serious enough to justify a 1.1.1 release (unless you count the SolrMarc Dewey indexing problems, which affect a fairly narrow group of users), and there are soon going to be changes that will make upgrading complex (particularly the Solr 3.1 update and expanded ILS driver functionality).  We discussed whether we want to continue targeting a 1.1.1 release, or whether it makes more sense to jump directly to a 1.2 release.  The general consensus was that we should skip 1.1.1 and update the next release number to 1.2; we can always build a 1.1.1 version by copying and patching the 1.1 release if there is sufficient demand.
@@ Line 63: / Line 68: @@
 Demian has been approached by Elsevier to help develop a simple app for the [[http://www.sciverse.com|SciVerse platform]] to embed VuFind results into the platform.  This will be open sourced and made available to any interested VuFind libraries.  SciVerse is based on the OpenSocial standard, so the app is also probably easily adaptable to related platforms like Google.  It currently works by using RSS feeds, the least-common-denominator approach for compatibility with the broadest range of VuFind installations.  If you are interested in working on something more elaborate, please let Demian know.
 ==== 10. Other Topics? ====
+Luke's QR code logic is in use at the SWWHEP VuFind instance; for example, [[https://ifind.swwhep.ac.uk/discover/Record/SU97817|try this link]].  There was some discussion of what data should be encoded in QR codes (links or text); this option should probably be made configurable if QR codes make it into the trunk.
 ===== Next Call =====
@@ Line 70: / Line 78: @@
 The next call will be Tuesday, May 3, 2011 at 10am Eastern Daylight Time (GMT - 4:00).
 ---- struct data ----
+properties.Page Owner :
 ----