[Buildbot-commits] buildbot ChangeLog,1.502,1.503 NEWS,1.44,1.45

[Brian Warner]

Update of /cvsroot/buildbot/buildbot
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2622

Modified Files:
	ChangeLog NEWS 
Log Message:
Revision: arch at buildbot.sf.net--2004/buildbot--dev--0--patch-315
Creator:  Brian Warner <warner at lothar.com>

NEWS: start adding items for the next release

	* NEWS: start adding items for the next release


Index: ChangeLog
===================================================================
RCS file: /cvsroot/buildbot/buildbot/ChangeLog,v
retrieving revision 1.502
retrieving revision 1.503
diff -u -d -r1.502 -r1.503
--- ChangeLog	3 Sep 2005 19:50:00 -0000	1.502
+++ ChangeLog	3 Sep 2005 19:50:17 -0000	1.503
@@ -1,5 +1,7 @@
 2005-09-03  Brian Warner  <warner at lothar.com>
 
+	* NEWS: start adding items for the next release
+
 	* docs/examples/twisted_master.cfg: (sync with reality) turn off
 	python2.2 tests, change 'Quick' builder to only use python2.3
 

Index: NEWS
===================================================================
RCS file: /cvsroot/buildbot/buildbot/NEWS,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- NEWS	23 May 2005 22:48:05 -0000	1.44
+++ NEWS	3 Sep 2005 19:50:17 -0000	1.45
@@ -1,5 +1,61 @@
 User visible changes in Buildbot.
 
+* Release x.x.x (xx)
+
+* new features
+
+** new c['schedulers'] config-file element (REQUIRED)
+
+The code which decides exactly *when* a build is performed has been massively
+refactored. YOU MUST UPDATE your master.cfg files to match: in general this
+will merely require you to add an appropriate c['schedulers'] entry. Any old
+".treeStableTime" settings on the BuildFactory instances will now be ignored.
+The user's manual has complete details with examples of how the new Scheduler
+classes work.
+
+** c['interlocks'] removed, Locks and Dependencies now separate items
+
+The c['interlocks'] config element has been removed, and its functionality
+replaced with two separate objects. Locks are used to tell the buildmaster
+that certain Steps or Builds should not run at the same time as other Steps
+or Builds (useful for test suites that require exclusive access to some
+external resource: of course the real fix is to fix the tests, because
+otherwise your developers will be suffering from the same limitations). The
+Lock object is created in the config file and then referenced by a Step
+specification tuple or by the 'locks' key of the Builder specification
+dictionary.
+
+When you want to have one Build run or not run depending upon whether some
+other set of Builds have passed or failed, you use a special kind of
+Scheduler defined in the scheduler.Dependent class. This scheduler watches an
+upstream Scheduler for builds of a given source version to complete, and only
+fires off its own Builders when all of the upstream's Builders have built
+that version successfully.
+
+Both features are fully documented in the user's manual.
+
+** 'try'
+
+The 'buildbot try' feature has finally been added. There is some
+configuration involved, both in the buildmaster config and on the developer's
+side, but once in place this allows the developer to type 'buildbot try' in
+their locally-modified tree and to be given a report of what would happen if
+their changes were to be committed. This works by computing a (base revision,
+patch) tuple that describes the developer's tree, sending that to the
+buildmaster, then running a build with that source on a given set of
+Builders. The 'buildbot try' tool then emits status messages until the builds
+have finished.
+
+'try' exists to allow developers to run cross-platform tests on their code
+before committing it, reducing the chances they will inconvenience other
+developers by breaking the build. The UI is still clunky, but expect it to
+change and improve over the next few releases.
+
+Instructions for developers who want to use 'try' (and the configuration
+changes necessary to enable its use) are in the user's manual.
+
+
+
 * Release 0.6.6 (23 May 2005)
 
 ** bugs fixed