post-review is a command line tool for Windows, Linux and MacOS X
that simplifies both creating and updating review requests. It
can look at your source directory, generate a diff, and upload it
to a new or existing review request on an associated Review Board
server. This saves a lot of time over the web UI, and for some
types of code repositories (such as Perforce), its actually required
in order to produce a compatible diff.
default in mk/defaults/mk.conf
remove the non-shared defaults and put in the setting that actually gets
used by more than one package (namely, MAJORDOMO_HOMEDIR)
don't make the majordom user own more than it actually needs to
make resend, archive, request-answer and medit honor the MAJORDOMO_CF
environment variable over the command line option, so that someone calling
these via the wrapper (which sets the environment variable) can't make
the majordom user execute random perl code by specifying it as config file.
Thanks to salo for finding this issue.
* Fixed the build process for MacOS X.
* Re-activeted vigra-config (script to query VIGRA installation information)
and added VigraConfig.cmake (query VIGRA installation information from within
cmake).
* Added CDash support (nightly builds and tests).
* Added convexHull().
* Added vigra::Box.
* Added vigra::Sampler class to sample given data in various ways.
* Added much new functionality to the vigra::RandomForest class (e.g. more
split strategies, variable importance measures, feature selection)
* Added readSIF() (reader for the Andor SIF file format).
* Added vigra::HDF5File for easier navigation in HDF5 files.
* Added recursive approximation of the Gaussian filter
(recursiveGaussianFilterX(), recursiveGaussianFilterY())
* vigranumpy: added Gabor filtering.
* Fixed multi-threading bugs at various places.
* Minor improvements and bug fixes in the code and documentation.
require this.
* Release 0.6.1 (16-Jan-2011)
** Minor Fixes
The old "sets" module is no longer imported without wrapping the import in a
DeprecationWarning suppressor. We still import it from slicers.set for
compatibility with older code, but that import will not produce a warning.
This should make Foolscap quieter when used with Python 2.6 or later.
A new RemoteReference method named getDataLastReceivedAt() was added, which
will tell you when data was most recently received on the connection
supporting that reference. This can be compared against time.time() to see
how "live" the connection is. For performance reasons, this is only enabled
when keepalives are turned on, otherwise it returns None. (#169)
Some unreachable code was removed. (#165)
* Release 0.6.0 (28-Dec-2010)
** API Changes
*** "foolscap.api" now mandatory
The old import names from foolscap/__init__.py have been removed, finishing
the transition begun with 0.5.0 . Applications must now import Tub,
Referenceable, and so on from "foolscap.api". (#122)
** Compatibility Fixes
Foolscap-0.6.0 is compatible with Twisted-10.2 (released 29-Nov-2010). The
0.5.1 release was not: pb.Listener was depending upon the behavior of an
internal Twisted function that changed, causing an AttributeError in
"StreamServerEndpointService". This is fixed, but the code is still using an
undocumented internal attribute to handle port=0 which will need to be
replaced eventually. (#167)
The first unit test ("test__versions") spuriously failed against Twisted-10.1
and 10.2, mistakenly believing that 10.1 was older than 8.1.0 due to a
lexicographic comparison that should have been numeric.
** Other Changes
Incident filenames are now like "2008-08-22--16:20:28Z.flog" which are in UTC
and mostly ISO-8601 format (the real ISO-8601 would use "_" instead of "--").
This is also used for log-gatherer filenames. (#111)
The logging code now honors FLOGLEVEL= when using FLOGTOTWISTED=1; previously
FLOGLEVEL= was ignored when deciding which log events should be bridged to
the twisted logger. (#154)
Some minor packaging bugs were fixed.
mock is a Python module that provides a core Mock class. It removes
the need to create a host of stubs throughout your test suite. After
performing an action, you can make assertions about which methods /
attributes were used and arguments they were called with. You can
also specify return values and set needed attributes in the normal
way.
