#################### Bazaar Release Notes #################### .. toctree:: :maxdepth: 1 bzr 2.5b2 ######### :2.5b2: NOT RELEASED YET External Compatibility Breaks ***************************** .. These may require users to change the way they use Bazaar. New Features ************ .. New commands, options, etc that users may wish to try out. * A new ``-O`` standard option (common to all commands) have been added. It provides a value for a config option in the ``-Oname=value`` form that takes precedence over all definitions found in config files. It can be used multiple times to override different options. (Vincent Ladeuil, #491196) * ``bzr serve`` will now disconnect clients if they have not issued an RPC request after 5minutes. On POSIX platforms, this will also happen for ``bzr serve --inet``. This can be overridden with the configuration variable ``serve.client_timeout`` or in the command line parameter ``bzr serve --client-timeout=X``. Further, it is possible to request ``bzr serve [--inet]`` to shutdown gracefully by sending SIGHUP. It will finish the current request, and then close the connection. (John Arbash Meinel, #824797, #795025) Improvements ************ .. Improvements to existing commands, especially improved performance or memory usage, or better results. * Fixed a bug where ``bzr tags -r x..y`` loaded the branch history once for every revision in the range; it's now much faster. (Vincent Ladeuil, #857335) * ``bzr info -v`` can now be run against branches that don't support ``last_revision_info``, in which case the branch information will simply not be displayed. (Jelmer Vernooij) Bug Fixes ********* .. Fixes for situations where bzr would previously crash or give incorrect or undesirable results. * ``bzr shelve`` can now be used in emacs shells as the input handling is turned into a line-basde one when ``INSIDE_EMACS`` is set (which is the case for all recent emacs versions). (Vincent Ladeuil, #856261) * ``bzr tags`` can now be used against remote repositories that do not provide access to the revision graph. (Jelmer Vernooij, #858942) * ``bzr update PATH`` will stop if you seem to be asking it to update anything less than a whole tree, because that's not supported by bzr's concept that the whole tree has a single basis revision. Previously, it would go ahead and update the whole tree, which was surprising. (Martin Pool, #557886) * Don't crash if bzrlib.initialize() has not been called while accessing configs. (Vincent Ladeuil, #863401) * Redirects between http and https no longer discard path information in some cases. (Jelmer Vernooij, #853765) * The ``--overwrite`` argument to ``bzr push`` and ``bzr pull`` no longer reports all tags as changed. (Jelmer Vernooij, #845396) * ``WorkingTree.get_file_mtime`` now raises NoSuchId if a file id is specified that is unknown. (Jelmer Vernooij, #847435) Documentation ************* .. Improved or updated documentation. API Changes *********** .. Changes that may require updates in plugins or other code that uses bzrlib. * ``Branch.get_revision_delta`` has been deprecated. Use ``Repository.get_revision_delta`` instead. (Jelmer Vernooij, #859712) * ``Repository.fileids_altered_by_revision_ids`` has been moved to ``VersionedFileRepository`` and is no longer part of the standard ``Repository`` interface. (Jelmer Vernooij) * The new method ``ControlDirFormat.is_initializable()`` returns a boolean indicating whether or not it is possible to use any of the initialization methods of that format to create a new control dir. (Jelmer Vernooij) Internals ********* .. Major internal changes, unlikely to be visible to users or plugin developers, but interesting for bzr developers. * ``Branch`` objects can now use a config stack with the newly introduced ``get_config_stack()``. Both ``get_config`` and ``get_config_stack`` can be used for the same branch but it's recommended to stick to one for a given option. Testing ******* * Test scripts can now use ``bzr shelve`` and provide their input as complete lines. (Vincent Ladeuil, #856261) .. Fixes and changes that are only relevant to bzr's test framework and suite. This can include new facilities for writing tests, fixes to spurious test failures and changes to the way things should be tested. * Really corrupt the pack file without depending on a special length or value. (Vincent Ladeuil, #807032) bzr 2.5b1 ######### :2.5b1: 2011-09-15 This is the first beta of the 2.5 series, leading up to a 2.5.0 release in February 2012. Beta releases are suitable for everyday use but may cause some incompatibilities with plugins. Some plugins may need small updates to work with 2.5b1. External Compatibility Breaks ***************************** None New Features ************ * A ``from_unicode`` parameter can be specified when registering a config option. This implements boolean, integer and list config options when the provided ``bool_from_store``, ``int_from_store`` and ``list_from_store`` are used for this parameter. (Vincent Ladeuil) * Accessing a packaging branch on Launchpad (eg, ``lp:ubuntu/bzr``) now checks to see if the most recent published source package version for that project is present in the branch tags. This should help developers trust whether the packaging branch is up-to-date and can be used for new changes. The level of verbosity is controlled by the config item ``launchpad.packaging_verbosity``. It can be set to one of off disable all checks minimal only display if the branch is out-of-date short also display single-line up-to-date and missing, all (default) display multi-line content for all states (John Arbash Meinel, #609187, #812928) * Add a config option gpg_signing_key for setting which GPG key should be used to sign commits. Also default to using the gpg user identity which matches user_email() as set by whoami. (Jonathan Riddell, #68501) * An ``invalid`` parameter can be specified when registering a config option to decide what should be done when invalid values are encountered. 'warning' and 'error' will respectively emit a warning and ignore the value or errors out. (Vincent Ladeuil) * bzr add now skips large files in recursive mode. The default "large" size is 20MB, and is configurable via the add.maximum_file_size option. A value of 0 disables skipping. Named items passed to add are never skipped. (Shannon Weyrick, #54624) * ``bzr help configuration/