Next | Query returned 88 messages, browsing 61 to 70 | Previous

History of commit frequency

CVS Commit History:


   2008-07-20 11:02:51 by Eric Gillespie | Files touched by this commit (3) | Package updated
Log message:
- sort PLIST
- update to:

bzr 1.5 2008-05-16
------------------

This release of Bazaar includes several updates to the documentation, and fixes
to prepare for making rich root support the default format. Many bugs have been
squashed, including fixes to log, bzr+ssh inter-operation with older servers.

  CHANGES:

    * Suppress deprecation warnings when bzrlib is a 'final' release. This way
      users of packaged software won't be bothered with DeprecationWarnings,
      but developers and testers will still see them. (John Arbash Meinel)

  DOCUMENTATION:

    * Incorporate feedback from Jelmer Vernooij and Neil Martinsen-Burrell
      on the plugin and integration chapters of the User Guide.
      (Ian Clatworthy)

bzr 1.5rc1 2008-05-09
---------------------

  NOTES WHEN UPGRADING:

  CHANGES:

    * Broader support of GNU Emacs mail clients. Set
      ``mail_client=emacsclient`` in your bazaar.conf and ``send`` will pop the
      bundle in a mail buffer according to the value of ``mail-user-agent``
      variable. (Xavier Maillard)

  FEATURES:

  IMPROVEMENTS:

    * Diff now handles revision specs like "branch:" and \ 
"submit:" more
      efficiently.  (Aaron Bentley)

    * More friendly error given when attempt to start the smart server
      on an address already in use. (Andrea Corbellini, #200575)

    * Pull completes much faster when there is nothing to pull.
      (Aaron Bentley)

  BUGFIXES:

    * Authentication.conf can define sections without password.
      (Vincent Ladeuil, #199440)

    * Avoid muttering every time a child update does not cause a progress bar
      update. (John Arbash Meinel, #213771)

    * ``Branch.reconcile()`` is now implemented. This allows ``bzr reconcile``
      to fix when a Branch has a non-canonical mainline history. ``bzr check``
      also detects this condition. (John Arbash Meinel, #177855)

    * ``bzr commit`` now works with Microsoft's FTP service.
      (Andreas Deininger)

    * Catch definitions outside sections in authentication.conf.
      (Vincent Ladeuil, #217650)

    * Conversion from non-rich-root to rich-root(-pack) updates inventory
      sha1s, even when bundles are used.  (Aaron Bentley, #181391)

    * Conversion from non-rich-root to rich-root(-pack) works correctly even
      though search keys are not topologically sorted.  (Aaron Bentley)

    * Conversion from non-rich-root to rich-root(-pack) works even when a
      parent revision has a different root id.  (Aaron Bentley, #177874)

    * Disable strace testing until strace is fixed (see bug #103133) and emit a
      warning when selftest ends to remind us of leaking tests.
      (Vincent Ladeuil, #226769)

    * Fetching all revisions from a repository does not cause pack collisions.
      (Robert Collins, Aaron Bentley, #212908)

    * Fix error about "attempt to add line-delta in non-delta knit".
      (Andrew Bennetts, #217701)

    * Pushing a branch in "dirstate" format (Branch5) over bzr+ssh \ 
would break
      if the remote server was < version 1.2. This was due to a bug in the
      RemoteRepository.get_parent_map() fallback code.
      (John Arbash Meinel, #214894)

    * Remove leftover code in ``bzr_branch`` that inappropriately creates
      a ``branch-name`` file in the branch control directory.
      (Martin Pool)

    * Set SO_REUSEADDR on server sockets of ``bzr serve`` to avoid problems
      rebinding the socket when starting the server a second time.
      (John Arbash Meinel, Martin Pool, #164288)

    * Severe performance degradation in fetching from knit repositories to
      knits and packs due to parsing the entire revisions.kndx on every graph
      walk iteration fixed by using the Repository.get_graph API.  There was
      another regression in knit => knit fetching which re-read the index for
      every revision each side had in common.
      (Robert Collins, John Arbash Meinel)

    * When logging the changes to a particular file, there was a bug if there
      were ghosts in the revision ancestry. (John Arbash Meinel, #209948)

  DOCUMENTATION:

    * Expanded the User Guide to include new chapters on popular plugins and
      integrating Bazaar into your environment. The *Best practices* chapter
      was renamed to *Miscellaneous topics* as suggested by community
      feedback as well. (Ian Clatworthy)

    * Document outlining strategies for TortoiseBzr. (Mark Hammond)

    * Improved the documentation on hooks. (Ian Clatworthy)

    * Update authentication docs regarding ssh agents.
      (Vincent Ladeuil, #183705)

  TESTING:

    * Add ``thread_name_suffix`` parameter to SmartTCPServer_for_testing, to
      make it easy to identify which test spawned a thread with an unhandled
      exception. (Andrew Bennetts)

    * New ``--debugflag``/``-E`` option to ``bzr selftest`` for setting
      options for debugging tests, these are complementary to the the -D
      options.  The ``-Dselftest_debug`` global option has been replaced by the
      ``-E=allow_debug`` option for selftest. (Andrew Bennetts)

    * Parameterised test ids are preserved correctly to aid diagnosis of test
      failures. (Robert Collins, Andrew Bennetts)

    * The test suite modules have been modified to define load_tests() instead
      of test_suite(). That speeds up selective loading (via --load-list)
      significantly and provides many examples on how to migrate (grep for
      load_tests).  (Vincent Ladeuil)

  INTERNALS:

    * ``Hooks.install_hook`` is now deprecated in favour of
      ``Hooks.install_named_hook`` which adds a required ``name`` parameter, to
      avoid having to call ``Hooks.name_hook``. (Daniel Watkins)

    * Implement xml8 serializer.  (Aaron Bentley)

    * New form ``@deprecated_method(deprecated_in(1, 5, 0))`` for making
      deprecation wrappers.  (Martin Pool)

    * ``Repository.revision_parents`` is now deprecated in favour of
      ``Repository.get_parent_map([revid])[revid]``. (Jelmer Vernooij)

    * The Python ``assert`` statement is no longer used in Bazaar source, and
      a test checks this.  (Martin Pool)

  API BREAKS:

    * ``bzrlib.status.show_pending_merges`` requires the repository to be
      locked by the caller. Callers should have been doing it anyway, but it
      will now raise an exception if they do not. (John Arbash Meinel)

    * Repository.get_data_stream, Repository.get_data_stream_for_search(),
      Repository.get_deltas_for_revsions(), Repository.revision_trees(),
      Repository.item_keys_introduced_by() no longer take read locks.
      (Aaron Bentley)

    * ``LockableFiles.get_utf8`` is deprecated, as a start towards
      removing LockableFiles and ``.control_files`` entirely.
      (Martin Pool)

    * Methods deprecated prior to 1.1 have been removed.
      (Martin Pool)
   2008-07-14 14:56:20 by Joerg Sonnenberger | Files touched by this commit (563)
Log message:
Mark as destdir ready.
   2008-06-20 03:09:45 by Joerg Sonnenberger | Files touched by this commit (993)
Log message:
Add DESTDIR support.
   2008-05-05 13:17:51 by Juan Romero Pardines | Files touched by this commit (3)
Log message:
Update to 1.4:

This release of Bazaar includes handy improvements to the speed of log and
status, new options for several commands, improved documentation, and better
hooks, including initial code for server-side hooks.  A number of bugs have
been fixed, particularly in interoperability between different formats or
different releases of Bazaar over there network.  There's been substantial
internal work in both the repository and network code to enable new features
and faster performance.

BUG FIXES:

* Pushing a branch in "dirstate" format (Branch5) over bzr+ssh would break
  if the remote server was < version 1.2.  This was due to a bug in the
  RemoteRepository.get_parent_map() fallback code.
  (John Arbash Meinel, Andrew Bennetts, #214894)
   2008-04-25 22:39:14 by Joerg Sonnenberger | Files touched by this commit (170)
Log message:
Update PYTHON_VERSIONS_COMPATIBLE
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
   2008-04-16 16:44:44 by Juan Romero Pardines | Files touched by this commit (2)
Log message:
Update to 1.3.1:

* Fix a bug causing a ValueError crash in ``parse_line_delta_iter`` when
  fetching revisions from a knit to pack repository or vice versa using
  bzr:// (including over http or ssh).
  (#208418, Andrew Bennetts, Martin Pool, Robert Collins)
   2008-04-07 22:10:10 by Juan Romero Pardines | Files touched by this commit (3)
Log message:
Update to 1.3:

Many operations that act on history, including ``log`` and ``annotate`` are
now substantially faster.  Several bugs have been fixed and several new
options and features have been added.

And more, please review the NEWS file.
   2008-02-15 17:46:20 by Greg Troxel | Files touched by this commit (3)
Log message:
Update to 1.2 from Nick Goffee.

bzr 1.2 2008-02-15 (BUGFIXES and INTERNALS omitted)
------------------

bzr 1.2rc1 2008-02-13
---------------------

  NOTES WHEN UPGRADING:

    * Fetching via the smart protocol may need to reconnect once during a fetch
      if the remote server is running Bazaar 1.1 or earlier, because the client
      attempts to use more efficient requests that confuse older servers.  You
      may be required to re-enter a password or passphrase when this happens.
      This won't happen if the server is upgraded to Bazaar 1.2.
      (Andrew Bennetts)

  CHANGES:

    * Fetching via bzr+ssh will no longer fill ghosts by default (this is
      consistent with pack-0.92 fetching over SFTP). (Robert Collins)

    * Formatting of ``bzr plugins`` output is changed to be more human-
      friendly. Full path of plugins locations will be shown only with
      ``--verbose`` command-line option. (Alexander Belchenko)

    * ``merge`` now prefers to use the submit branch, but will fall back to
      parent branch.  For many users, this has no effect.  But some users who
      pull and merge on the same branch will notice a change.  This change
      makes it easier to work on a branch on two different machines, pulling
      between the machines, while merging from the upstream.
      ``merge --remember`` can now be used to set the submit_branch.
      (Aaron Bentley)

  FEATURES:

    * ``merge --preview`` produces a diff of the changes merge would make,
      but does not actually perform the merge.  (Aaron Bentley)

    * New smart method ``Repository.get_parent_map`` for getting revision
      parent data. This returns additional parent information topologically
      adjacent to the requested data to reduce round trip latency impacts.
      (Robert Collins)

    * New smart method, ``Repository.stream_revisions_chunked``, for fetching
      revision data that streams revision data via a chunked encoding.  This
      avoids buffering large amounts of revision data on the server and on the
      client, and sends less data to the server to request the revisions.
      (Andrew Bennetts, Robert Collins, #178353)

    * The launchpad plugin now handles lp urls of the form
      ``lp://staging/``, ``lp://demo/``, ``lp://dev/`` to use the appropriate
      launchpad instance to do the resolution of the branch identities.
      This is primarily of use to Launchpad developers, but can also
      be used by other users who want to try out Launchpad as
      a branch location without messing up their public Launchpad
      account.  Branches that are pushed to the staging environment
      have an expected lifetime of one day. (Tim Penhey)

  IMPROVEMENTS:

    * Creating a new branch no longer tries to read the entire revision-history
      unnecessarily over smart server operations. (Robert Collins)

    * Fetching between different repository formats with compatible models now
      takes advantage of the smart method to stream revisions.  (Andrew Bennetts)

    * The ``--coverage`` option is now global, rather specific to ``bzr
      selftest``.  (Andrew Bennetts)

    * The ``register-branch`` command will now use the public url of the branch
      containing the current directory, if one has been set and no explicit
      branch is provided.  (Robert Collins)

    * Tweak the ``reannotate`` code path to optimize the 2-parent case.
      Speeds up ``bzr annotate`` with a pack repository by approx 3:2.
      (John Arbash Meinel)

  API BREAKS:

    * Classes implementing Merge types like Merge3Merger must now accept (and
      honour) a do_merge flag in their constructor.  (Aaron Bentley)

    * ``Repository.add_inventory`` and ``add_revision`` now require the caller
      to previously take a write lock (and start a write group.)
      (Martin Pool)

  TESTING:

    * selftest now accepts --load-list <file> to load a test id list. This
      speeds up running the test suite on a limited set of tests.
      (Vincent Ladeuil)
   2008-01-22 01:49:17 by Greg Troxel | Files touched by this commit (3)
Log message:
Update to 1.1 from Nick Goffee of BBN Technologies via private mail.

For the full list of changes, see NEWS.

   [many bugfixes]

   * The syntax ``bzr diff branch1 branch2`` is no longer supported.
     Use ``bzr diff branch1 --new branch2`` instead. This change has
     been made to remove the ambiguity where ``branch2`` is in fact a
     specific file to diff within ``branch1``.

   * diff '--using' allows an external diff tool to be used for files.
     (Aaron Bentley)

   * New "lca" merge-type for fast everyday merging that also supports
     criss-cross merges.  (Aaron Bentley)

   * ``merge`` now warns when merge directives cause cherrypicks.
     (Aaron Bentley)

   * ``split`` now supported, to enable splitting large trees into smaller
     pieces.  (Aaron Bentley)

   * Reference material has now be moved out of the User Guide and added
     to the User Reference. The User Reference has gained 4 sections as
     a result: Authenication Settings, Configuration Settings, Conflicts
     and Hooks. All help topics are now dumped into text format in the
     doc/en/user-reference directory for those who like browsing that
     information in their editor. (Ian Clatworthy)

   * Annotate merge (merge-type=weave) now supports cherrypicking.
     (Aaron Bentley)

   * ``switch`` can now be used on heavyweight checkouts as well as
     lightweight ones. After switching a heavyweight checkout, the
     local branch is a mirror/cache of the new bound branch and
     uncommitted changes in the working tree are merged. As a safety
     check, if there are local commits in a checkout which have not
     been committed to the previously bound branch, then ``switch``
     fails unless the ``--force`` option is given. This option is
     now also required if the branch a lightweight checkout is pointing
     to has been moved. (Ian Clatworthy)

   * The default repository format is now ``pack-0.92``.  This
     default is used when creating new repositories with ``init`` and
     ``init-repo``, and when branching over bzr+ssh or bzr+hpss.
     (See https://bugs.launchpad.net/bugs/164626)

     This format can be read and written by Bazaar 0.92 and later, and
     data can be transferred to and from older formats.

     To upgrade, please reconcile your repository (``bzr reconcile``), and then
     upgrade (``bzr upgrade``).

     ``pack-0.92`` offers substantially better scaling and performance than the
     previous knits format. Some operations are slower where the code already
     had bad scaling characteristics under knits, the pack format makes such
     operations more visible as part of being more scalable overall. We will
     correct such operations over the coming releases and encourage the filing
     of bugs on any operation which you observe to be slower in a packs
     repository. One particular case that we do not intend to fix is pulling
     data from a pack repository into a knit repository over a high latency
     link;  downgrading such data requires reinsertion of the file texts, and
     this is a classic space/time tradeoff. The current implementation is
     conservative on memory usage because we need to support converting data
     from any tree without problems.
     (Robert Collins, Martin Pool, #164476)

   * The pack format is now accessible as "pack-0.92", or \ 
"pack-0.92-subtree"
     to enable the subtree functions (for example, for bzr-svn).
     See http://doc.bazaar-vcs.org/latest/developer/packrepo.html
     (Martin Pool)

   * New ``authentication.conf`` file holding the password or other credentials
     for remote servers. This can be used for ssh, sftp, smtp and other
     supported transports.
     (Vincent Ladeuil)

   * ``switch`` command added for changing the branch a lightweight checkout
     is associated with and updating the tree to reflect the latest content
     accordingly. This command was previously part of the BzrTools plug-in.
     (Ian Clatworthy, Aaron Bentley, David Allouche)

   * ``reconfigure`` command can now convert branches, trees, or checkouts to
     lightweight checkouts.  (Aaron Bentley)

   * ``bzr merge`` now warns when it encounters a criss-cross merge.
     (Aaron Bentley)
   2007-11-29 21:03:14 by Thomas Klausner | Files touched by this commit (3)
Log message:
Update to 0.92:

bzr 0.92 2007-11-05
===================

  CHANGES:

  * New uninstaller on Win32.  (Alexander Belchenko)

bzr 0.92rc1 2007-10-29
======================

  NOTES WHEN UPGRADING:

  CHANGES:

   * ``bzr`` now returns exit code 4 if an internal error occurred, and
     3 if a normal error occurred.  (Martin Pool)

   * ``pull``, ``merge`` and ``push`` will no longer silently correct some
     repository index errors that occured as a result of the Weave disk format.
     Instead the ``reconcile`` command needs to be run to correct those
     problems if they exist (and it has been able to fix most such problems
     since bzr 0.8). Some new problems have been identified during this release
     and you should run ``bzr check`` once on every repository to see if you
     need to reconcile. If you cannot ``pull`` or ``merge`` from a remote
     repository due to mismatched parent errors - a symptom of index errors -
     you should simply take a full copy of that remote repository to a clean
     directory outside any local repositories, then run reconcile on it, and
     finally pull from it locally. (And naturally email the repositories owner
     to ask them to upgrade and run reconcile).
     (Robert Collins)

  FEATURES:

   * New ``knitpack-experimental`` repository format. This is interoperable with
     the ``dirstate-tags`` format but uses a smarter storage design that greatly
     speeds up many operations, both local and remote. This new format can be
     used as an option to the ``init``, ``init-repository`` and ``upgrade``
     commands. See http://doc.bazaar-vcs.org/latest/developers/knitpack.html
     for further details. (Robert Collins)

   * For users of bzr-svn (and those testing the prototype subtree support) that
     wish to try packs, a new ``knitpack-subtree-experimental`` format has also
     been added. This is interoperable with the ``dirstate-subtrees`` format.
     (Robert Collins)

   * New ``reconfigure`` command. (Aaron Bentley)

   * New ``revert --forget-merges`` command, which removes the record of a pending
     merge without affecting the working tree contents.  (Martin Pool)

   * New ``bzr_remote_path`` configuration variable allows finer control of
     remote bzr locations than BZR_REMOTE_PATH environment variable.
     (Aaron Bentley)

   * New ``launchpad-login`` command to tell Bazaar your Launchpad
     user ID.  This can then be used by other functions of the
     Launchpad plugin. (James Henstridge)

  PERFORMANCE:

   * Commit in quiet mode is now slightly faster as the information to
     output is no longer calculated. (Ian Clatworthy)

   * Commit no longer checks for new text keys during insertion when the
     revision id was deterministically unique. (Robert Collins)

   * Committing a change which is not a merge and does not change the number of
     files in the tree is faster by utilising the data about whether files are
     changed to determine if the tree is unchanged rather than recalculating
     it at the end of the commit process. (Robert Collins)

   * Inventory serialisation no longer double-sha's the content.
     (Robert Collins)

   * Knit text reconstruction now avoids making copies of the lines list for
     interim texts when building a single text. The new ``apply_delta`` method
     on ``KnitContent`` aids this by allowing modification of the revision id
     such objects represent. (Robert Collins)

   * Pack indices are now partially parsed for specific key lookup using a
     bisection approach. (Robert Collins)

   * Partial commits are now approximately 40% faster by walking over the
     unselected current tree more efficiently. (Robert Collins)

   * XML inventory serialisation takes 20% less time while being stricter about
     the contents. (Robert Collins)

   * Graph ``heads()`` queries have been fixed to no longer access all history
     unnecessarily. (Robert Collins)

  IMPROVEMENTS:

   * ``bzr+https://`` smart server across https now supported.
     (John Ferlito, Martin Pool, #128456)

   * Mutt is now a supported mail client; set ``mail_client=mutt`` in your
     bazaar.conf and ``send`` will use mutt. (Keir Mierle)

   * New option ``-c``/``--change`` for ``merge`` command for cherrypicking
     changes from one revision. (Alexander Belchenko, #141368)

   * Show encodings, locale and list of plugins in the traceback message.
     (Martin Pool, #63894)

   * Experimental directory formats can now be marked with
     ``experimental = True`` during registration. (Ian Clatworthy)

  DOCUMENTATION:

   * New *Bazaar in Five Minutes* guide.  (Matthew Revell)

   * The hooks reference documentation is now converted to html as expected.
     (Ian Clatworthy)

Next | Query returned 88 messages, browsing 61 to 70 | Previous