[Checkins] SVN: zopetoolkit/doc/source/releaseteam/ add meeting notes for 11/23 and 12/07

Jan-Wijbrand Kolman janwijbrand at gmail.com
Wed Dec 8 05:23:02 EST 2010


Log message for revision 118757:
  add meeting notes for 11/23 and 12/07

Changed:
  U   zopetoolkit/doc/source/releaseteam/index.rst
  A   zopetoolkit/doc/source/releaseteam/meeting-20101123.rst
  A   zopetoolkit/doc/source/releaseteam/meeting-20101207.rst

-=-
Modified: zopetoolkit/doc/source/releaseteam/index.rst
===================================================================
--- zopetoolkit/doc/source/releaseteam/index.rst	2010-12-08 09:26:01 UTC (rev 118756)
+++ zopetoolkit/doc/source/releaseteam/index.rst	2010-12-08 10:23:02 UTC (rev 118757)
@@ -23,4 +23,6 @@
     meeting-20100907
     meeting-20100921
     meeting-20101109
+    meeting-20101123
+    meeting-20101207
     package-usage

Added: zopetoolkit/doc/source/releaseteam/meeting-20101123.rst
===================================================================
--- zopetoolkit/doc/source/releaseteam/meeting-20101123.rst	                        (rev 0)
+++ zopetoolkit/doc/source/releaseteam/meeting-20101123.rst	2010-12-08 10:23:02 UTC (rev 118757)
@@ -0,0 +1,52 @@
+ZTK meeting - 2010-11-23
+========================
+
+Attendance
+----------
+
+j-w, hannosch, ccomb.
+
+Agenda
+------
+
+- Discussion
+- Tasks
+- Planning the next meeting
+
+Discussion
+----------
+
+* j-w moved the zope.app. packages to the deprecated-section.
+
+* There was a short discussion on zope-dev about using distribute
+  versus setuptools. The releaseteam conclusion was not to introduce
+  any (implicit) dependencies on either. Hannosh suggested to test the
+  ZTK packages for (unintentional) dependencies on distribute.
+
+* There're a few ZTK packages trunks that refer to yet-unreleased
+  versions of their dependencies. This means, these trunk a hard to
+  release, but more importantly, these packages will not be easily
+  testable in buildbots.
+
+  Various options were discussed including: using mr.developer and its
+  auto-checkout features, refrain from testing trunks in buildbot or
+  have developments done on a packages that requires a new release of
+  a dependency, done on development branches. This latter seems to be
+  the sensible approach.
+
+  J-w will make a list of packages trunks that have this issue.
+
+Tasks
+-----
+
+* Check for ZTK packages that would rely on distribute [hannosch]
+
+* Check for package trunks that rely on yet unreleased version of its
+  dependencies [j-w]
+
+* Update the version in the ZTK [ccomb]
+
+Next meeting
+------------
+
+Next meeting is scheduled for December 7th 20:30 (CET) on #zope.

Added: zopetoolkit/doc/source/releaseteam/meeting-20101207.rst
===================================================================
--- zopetoolkit/doc/source/releaseteam/meeting-20101207.rst	                        (rev 0)
+++ zopetoolkit/doc/source/releaseteam/meeting-20101207.rst	2010-12-08 10:23:02 UTC (rev 118757)
@@ -0,0 +1,36 @@
+ZTK meeting - 2010-12-07
+========================
+
+Attendance
+----------
+
+j-w, hannosch.
+
+Agenda
+------
+
+- Discussion
+- Tasks
+- Planning the next meeting
+
+Discussion
+----------
+
+The tasks of last meeting were not handled yet. Since no new issues
+came up in the meantime and ccomb was not able to make to the meeting
+it in time, it was decided to adjourn the meeting until December 14th.
+
+Tasks
+-----
+
+* Check for ZTK packages that would rely on distribute [hannosch]
+
+* Check for package trunks that rely on yet unreleased version of its
+  dependencies [j-w]
+
+* Update the version in the ZTK [ccomb]
+
+Next meeting
+------------
+
+Next meeting is scheduled for December 14th 20:30 (CET) on #zope.



More information about the checkins mailing list