Changes between Initial Version and Version 1 of DevMtgMinutes/20080918

Timestamp:

Jan 23, 2009, 3:26:42 PM (17 years ago)

Author:

Conrad Huang

Comment:

--

DevMtgMinutes/20080918

@@ +1 @@
+== September 18, 2008 ==
+'''Attendees''': tef, Tom, Elaine, Greg, Eric, Scooter, Conrad
+
+=== New Action Items ===
+ - Eric will send e-mail to Craig Gough and Bo Yang Baker about retirement of spinoza and euler (item 1a)
+
+=== Action Items from previous meetings ===
+ - Al will decommission SGI after the next Chimera production release
+ - Al will install stereo-capable workstation to replace SGI before decommissioning SGIs
+ - tef will contact Adobe for more information about embedding 3d graphics in PDF documents
+ - Conrad will fix daily build script to copy app and build tree to desktop machines
+ - Greg will implement OpenGL-feature-usage interface
+
+=== Minutes ===
+ 1. Review Action Items
+  a.  Greg checked SGI activity and found only four users: Ed Pate (visitor), Ben Webb (MODELLER builds), Craig Gough and Bo Yang Baker. Eric reported that the last two are no longer at UCSF and will contact them regarding impending retirement of SGI machines.  A stereo-capable workstation will be made available for public (Pate) use before SGIs are turned off.  An Octane will be "donated" to QB3 machine room for MODELLER builds (Webb).
+  b.  Greg reported that the OpenGL preference panel code has been designed and will be implemented in one week.
+  c.  Tom contacted Sebastien who said that he is actively promoting the use of Volume Series.  Consensus is to keep Volume Series in Chimera for now.
+  d.  tef contacted Miracube and is getting a new 24" LCD panel for evaluation (will arrive in a couple weeks).  Unit will arrive with two pairs of stereo glasses.  If testing goes well, we will purchase the unit for a discounted price of $3,900 (list if $4,900).
+  e.  Scooter will discuss Wiki technology during group meeting when demonstrating Trac.
+ 2. Discuss source tree forking mechanism (Scooter)
+  a.  Scooter discussed tree forking in CVS using example from http://users.csc.calpoly.edu/~jdalbey/205/Resources/cvsBranchMerge.html  The example web page has examples on how to tag a branch, switch between branches, merging branches, etc.
+  b.  General practice is to keep a separated checked out tree for each branch.  Changes should be made on the branch where it should first appear, e.g., bug fixes in the candidate release branch and new features in trunk.  Bug fixes in the branch that also need to be in the trunk can be added back using the "cvs update -j release-name filename" command in the trunk tree.
+  c.  With branching, Chimera versioning using RCS/CVS version number may produce duplicate version strings for builds on different branches. Consensus is to use a four-number versioning system (major.minor.bugfix[build]) starting with the next release.  The "major", "minor" and "bugfix" numbers need to be maintained manually, while the "build" can still be from RCS/CVS.  After forking the tree, the minor number on the trunk should be incremented immediately so that the branch and trunk are easily distinguishable.
+  d.  Upcoming release will be "1.3.0[build_no]".  1.3 was chosen because current release is 1.2540 so if you squint and only look at the first part, the "natural" small version number is "1.2"; and "1.3" comes after "1.2".  The candidate release branch will be 1.3; the trunk will be updated to 1.4 after forking.
+  e.  The source tree will be forked for candidate release after OpenGL preference panel is completed.
+
+Items below were tabled when meeting ended at 4pm.
+
+ * Discuss test lab, viz room and public cubicle setup (Conrad)
+ * Continue evaluation of features to remove or improve (All)