Codebase list ros-bloom / upstream/0.5.15 CHANGELOG.rst
upstream/0.5.15

Tree @upstream/0.5.15 (Download .tar.gz)

CHANGELOG.rst @upstream/0.5.15raw · history · blame

0.5.15 (2014-12-08 12:10:00 -0700)
----------------------------------
- Added support for REP 143 which allows for multiple distribution files, currently bloom uses the last one.
- Fix to Python3 support.
- ``ROSDISTRO_INDEX_URL``'s which point to githubusercontent.com will also be eligible for pull requests now.
- ``-DNDEBUG`` is now added to debian configurations by default.

0.5.14 (2014-11-26 08:10:00 -0700)
----------------------------------
- Hotfix for issue #329 which makes sure no extra new lines are introduced in the debian control file.
- Changed RPM build directory to have a more unique name.

0.5.13 (2014-11-24 17:10:00 -0700)
----------------------------------
- Fixed exception from importing ``bloom.logging``.
- Debian ``gbp.conf`` now uses ``upstream-tag``.
- Fixed a bug which overwrote the user provided debian folder during templating.
- Added support for utilizing the Conflicts and Replaces in ``package.xml``'s in the Debian control files.

0.5.12 (2014-09-24 15:28:16 -0700)
----------------------------------
- Pull requests are now opened against the commit from which the rosdistro index file is retrieved.
  This should address the remaining race condition in bloom allows pull requests which modify other entries.
  Addresses: `#252 <https://github.com/ros-infrastructure/bloom/issues/252>`_
- Pagination is now used when listing branches from GitHub.
  This addresses an error which occurred when the user had too many branches for page one.
  Addresses: `#273 <https://github.com/ros-infrastructure/bloom/issues/273>`_
- Improved support for unicode in changelogs.
  Addresses: `#260 <https://github.com/ros-infrastructure/bloom/issues/260>`_
- Added checking for .git and https on source and doc urls.
  Addresses: `#271 <https://github.com/ros-infrastructure/bloom/issues/271>`_
- Added check to make sure the release repository and the upstream repository are not the same.
  Addresses: `#267 <https://github.com/ros-infrastructure/bloom/issues/267>`_
- Added a check to make sure the changelog versions are sane with respect to the current version being released.
- Users can now skip rpm generation if rosdep keys are missing for fedora only.
- Improved error handling when GitHub's two factor authentication is encountered.
- Fixed a bug with expanding nested tarball's.
- Fixed order of changelogs in rpm generators.
- Non-interactive mode now applies to the confirmation for opening a pull request.

0.5.11 (2014-07-24 14:28:03 -0700)
----------------------------------
- Added rosrpm generator to the default list of generators.
- Upstream repository url and release repository url are now included in the summaries in pull requests.
- Updated the warning about changing track actions to make the transition of rosrpm in the default actions smoother.

0.5.10 (2014-06-16 11:48:51 -0700)
----------------------------------
- Fix cleaning behavior for trim and rebase, #281
- Fix a bug where stdout was getting truncated before a user prompt

0.5.9 (2014-05-22 14:55:59 -0700)
---------------------------------
- Revert to deb compat version 7 for Oneric

0.5.8 (2014-05-16 16:17:38 -0700)
---------------------------------
- Change deb compat version to 9 in order to get default compiler flags (with optimization) again

0.5.7 (2014-05-08 14:00:00 -0700)
---------------------------------
- Add versioned dependency on catkin_pkg 0.2.2

0.5.6 (2014-05-07 17:16:43 -0700)
---------------------------------
- When generating Debian and Fedora packaging files, explicitly include buildtool_export_depends with run_depends

0.5.5 (2014-05-01 10:24:31 -0700)
---------------------------------
- Add noarch flag to fedora generation for metapackages and packages marked as architecture_independent
- Fix the order of the arguments for git-bloom-config copy

0.5.4 (2014-04-11 16:09:00 -0700)
---------------------------------
- Fixed a problem with the documentation on readthedocs.org

0.5.3 (2014-04-11 15:51:09 -0700)
---------------------------------
- Fixed a bug when handling unicode failed on values which were int's
- Removed mention of username and hostname from bloom summaries in the release repo's README.md
- Fixed unicode handling in Fedora generation
- Modified handling of test dependencies for changes from REP-140 roll out
- Removed references to python-distribute in favor of python-setuptools
- Changed usuage of rosdep api to work with rosdep >= 0.10.27

0.5.2 (2014-03-04 20:52:09 -0600)
---------------------------------
- Pull request titles and body are now santized before printing
- Prevent unicode getting into the yaml files
- Make license tags required (rpm generation)
  Source RPMs will not build if the license tag is empty or missing.
  This will not be a problem for the vast majority of packages in ROS.
- Packages are now ordered in changelog summary
- Improved unicode support in Python2
- setup environment is now sourced before the install step (debian rules file)

0.5.1 (2014-02-24 16:03:29 -0800)
---------------------------------
- fix a bug related to setting the status description

0.5.0 (2014-02-23 21:55:00 -0800)
---------------------------------
- OAUTH is now used for creating pull requests.
  On the first pull request, bloom will ask for your github username and password.
  Using them it will create an authorization on your behalf and store it in your home folder.
  Specifically `~/.config/bloom`.
  From then on, bloom will no longer require your username and password for pull requests.
  Closed #177 and #170.
- Added checks to ensure that for github.com urls provided by users they end in `.git` and are `https://`
- Added some fixes and monkey patches to empy to better support unicode in changelogs
- Added additionally pull request checks, which should prevent some of the invalid pull requests from being created.
- Fixed a bug where packages which were removed from the repository were still getting generated.
- Merged preliminary Fedora generation support, provided by @cottsay
- Added changelog summaries to pull requests
- Added a prompt for users to enter doc, source, and maintenance status when releasing.

0.4.9 (2014-02-06 14:05:47 -0800)
---------------------------------
- Fixed another bug for first time releases, specifically first time releases which already have doc or source entries

0.4.8 (2014-01-29 14:19:24 -0600)
---------------------------------
- Fixed a bug for first time releases

0.4.7 (2014-01-24 15:50:00 -0800)
---------------------------------
- Fix bug in pull request opening with new rosdistro format

0.4.6 (2014-01-24 15:33:00 -0800)
---------------------------------
- Updates to support REP-0141 with rosdistro >= 0.3.0 and rosdep >= 0.10.25
- @ahendrix contributed an option for doing ssh key based pull request generation

0.4.5 (2014-01-22 10:58:50 -0800)
---------------------------------
- Added Python2/3 bilingual support, bloom should now install and work with Python3
- Added an assertion that the rosdistro version 1 is being used in preperation of REP-0141 roll out
- Fixed crash from unicode characters in the changelog
- Added assertions about the format of version numbers used
- Added check for git submodules, still not supported, but bloom will fail earlier with a better error
- Fixed a bug where empty folders containing a .gitignore in the upstream caused bloom to fail

0.4.4 (2013-07-22 17:50:55 -0700)
---------------------------------
- Properly handle pagination of github pages #174
- Made the pull request branch names more unique to avoid collisions in parallel releasing situations #178
- Disabled automatic opening of the webbrowser on Linux and added an option to disable it otherwise #162
- Fixed a problem where permissions where lost on templates, this applied specifically to loosing the executable flag on the debian rules file #179
- Only put the first maintainer listed in the debian/control file to prevent lintian errors #183

0.4.3 (2013-07-19 16:37:23 -0700)
---------------------------------
- Fixed a bug with creating new tracks
- Fixed a bug where the debian changelog would be wrong if a CHANGELOG.rst existed for the package, but there was no entry for this version being release
- Fixed a bug where the colorization of the diff could cause a crass to occur
- Added a versioned dependency on rosdistro-0.2.12, which addresses a rosdistro file formatting bug
- Fixed some issues with the stand alone rosdebian generator
- Temporary fix for github pagination problems

0.4.2 (2013-06-27 11:20:25 -0700)
---------------------------------
- Improved logging system slightly.
- Fixed the way logs are renamed after closing.
- Fixed a bug where names were not debian'ized for packages which rosdep could not resolve. #163
- Fixed a bug where a diff of the rosdistro file would fail when packages were being removed. #165
- Fixed a bug where upconverting repository configs could fail if a track.yaml and a bloom.conf existed. #166

0.4.1 (2013-06-25 12:17:13 -0700)
---------------------------------
- Fixed a bug which occurred on repositories with no previous releases. #158
- Fixed a bug where safety warnings were being printed when they should not have been. #159
- Fixed a bug where repositories with multiple packages did not consider peer packages when resolving rosdep keys. #160

0.4.0 (2013-06-19 17:13:36 -0700)
---------------------------------
- Automated Pull Requests have been re-enabled, but now the .netrc file is **not** used.
- REP-0132 CHANGELOG.rst files are now parsed and inserted into generated debian changes files.
- bloom now summarizes activity on the master branch, which is useful for figuring out what has been released recently.
- There is a new command bloom-generate, which allows generators to expose a stand alone generation command. For example, you can now run ``bloom-generate debian`` in a single catkin package and it will generate the needed files in the local ``debian`` folder. Addresses #121
- The command line options for ``bloom-release`` have been changed to be more explicit.
- The ``bloom`` branch is now deprecated, the ``master`` branch now holds all configurations and upstream overlay files. The ``bloom`` branch can be deleted after the automatic upgrade where bloom moves the needed files from the ``bloom`` branch to the ``master`` branch.
- Fuerte is no longer supported; this is because supporting fuerte was complicating the code base, use an older version of bloom (0.3.5) for fuerte releases.
- Packages can now be explicitly ignored by bloom by putting their names (separated by whitespace) in the <track>.ignored file in the master branch.
- Deprecated rosdep calls have been replaced with rosdistro.
- bloom now logs all output to log files in the ``~/.bloom_logs`` folder.
- Fixed several bugs:

    - Fixed use of tar as a vcs type #149
    - Fixed a bug where ``--new-track``'s changes would not take affect #147
    - bloom now allows a debian folder to already exist, overlaying other generated files #146
    - bloom now allows for an alternative release repository url which is used for pushing #137

0.3.5 (2013-04-17 11:03:50 -0700)
---------------------------------
- Temporarily disable automated pull requests while the new rosdistro format is being deployed.
- bloom now suggests likely alternatives when a repository is not found in the release file.

0.3.4 (2013-04-09 16:36:55 -0700)
---------------------------------
- Fixed a bug in the update notifier where the first run after updating still reports that bloom is out of date. #129
- bloom-release now respects global arguments like --version and --debug
- Improved messages around the cloning/pushing back of the working copy which takes a long time on large repos.
- Improved pull request failure message, indicating that the release was successful, but the pr was not. #131
- Fixed versioned dependencies in debians and setup.py. #130
- Fixed a bug with empty ~/.netrc files. #131
- General improvements with the automated pull request mechanism. #135
- Checks for valid metapackages using catkin_pkg now, adds version dependency of catkin_pkg at 0.1.11. #134

0.3.3 (2013-04-01 14:04:00 -0700)
---------------------------------
- bloom no longer allows users to release metapackages which do not have a CMakeLists.txt. See: `REP-0127 <http://ros.org/reps/rep-0127.html#metapackage>`_
- Fixed a bug related to gathering of package meta data on hg and svn repositories. #111
- Fixed a bug in git-bloom-patch which prevented users from running it directly. #110
- Fixed a bug where patches would not get applied after exporting them manually. #107
- Worked around a bug in vcstools which would not allow hg repositories to checkout to existing, empty directories. #112
- All git-bloom-* scripts now assert that they are in the root of a git repository. #113
- Added PEP8 check to the automated tests.
- bloom-release will now offer the user a git push --force if non-force fails.
- Added git-bloom-config [copy|rename] commands.
- Fixed a bug in the bloom.git.checkout api where it would return 0 on success, but should return True. #122
- bloom-release will now prompt the user for the release repository url if it is not in the rosdistro file. #125
- bloom-release will now offer to automatically open a pull-request for the user, if the user's .netrc file is setup for github. #126

0.3.2 (2013-03-06 17:49:51 -0800)
---------------------------------
- Fixed a bug in vcs url templating.
- Improved the performance of git-bloom-config.
- Added an --unsafe global option which will disable some of the safety mechanisms in bloom, making releasing about twice as fast but at the expense of errors putting the local release repository in an inconsistent state. Use with caution.
- Added support for templating stack.xml files like package.xml files in the import-upstream step.
- Fixed a bug where bloom failed if you call it and you were not on a branch
- Added global arguments to some commands which were still lacking them
- Fixed a bug where bloom would create None/<version> tags (these should be deleted manually if found)
- Got the automated tests fixed and running in travis again
- Added emoji icons for OS X users with lion or greater

0.3.1 (2013-02-26 18:00:47 -0800)
---------------------------------
- Fixed handling of non-standard archive names in git-bloom-import-upstream.
  This was a bug where if the archive only had the name of the package then it would fail to be processed by import-upstream.
- Fixed an issue when blooming from svn upstream.
  This issue was caused by improperly handling the release_tag configuration when dealing with svn

0.3.0 (2013-02-26 14:04:21 -0800)
---------------------------------
- Generators can now be added using the distribute entry_points machanism
- There is now a debian/<rosdistro>/<package_name> branch before forking into debian/<rosdistro>/<debian_distro>/<package_name>
  The debian/<rosdistro> branch now contains the untemplated debain files, so that they can be patched before being templated.
- Users are now dropped into a shell when patch merging fails, allowing them to resolve the problem and continue.
- New generator rosrelease, makes the release tag release/<rosdistro>/<package_name> instead of release/<package_name>
- Bloom now checks to see if it is the latest version available and warns if it is not
- Configurations are now stored in "tracks" so that there can be multiple release configurations in each release repository
- New command bloom-export-upstream, this command creates an archive (tar.gz) of upstream given a uri, type, and reference to archive
- Refactored git-bloom-import-upstream, this command only takes an archive (tar.gz) now
- Configurations are now stored on the bloom branch in YAML
- git-bloom-release now takes only one argument, the release track to execute
- Files can be automatically overlaid onto upstream using a patches folder in the bloom branch
  This allows you to put a package.xml onto upstream without a patch in the release branch.
- package.xml files overlaid onto upstream branch from the patches folder in the bloom branch are templated on the version
- Release tags now contain release increment numbers, similar to the debian increment numbers, e.g. release/groovy/foo/0.1.0 is now release/groovy/foo/0.1.0-0
- New command bloom-release <repository> [<track>], which will release a repository end-to-end
  It will fetch the release repository using info from the ROS distro file, run bloom, then push the results