Hello community,

here is the log from the commit of package rubygem-capistrano for 
openSUSE:Factory checked in at 2014-01-23 14:03:57
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-capistrano (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-capistrano.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-capistrano"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-capistrano/rubygem-capistrano.changes    
2013-11-24 18:12:18.000000000 +0100
+++ 
/work/SRC/openSUSE:Factory/.rubygem-capistrano.new/rubygem-capistrano.changes   
    2014-01-23 15:55:50.000000000 +0100
@@ -1,0 +2,33 @@
+Mon Jan 20 09:29:44 UTC 2014 - [email protected]
+
+- updated to version 3.1.0
+ Breaking changes:
+ 
+   * `deploy:restart` task **is no longer run by default**.
+     From this version, developers who restart the app on each deploy need to 
declare it in their deploy flow (eg `after 'deploy:publishing', 
'deploy:restart'`).
+ 
+     Please, check 
https://github.com/capistrano/capistrano/commit/4e6523e1f50707499cf75eb53dce37a89528a9b0
 for more information. (@kirs)
+ 
+ * Minor changes
+   * Tasks that used `linked_dirs` and `linked_files` now run on all roles, 
not just app roles (@mikespokefire)
+   * Tasks `deploy:linked_dirs`, `deploy:make_linked_dirs`, 
`deploy:linked_files`, `deploy:cleanup_rollback`,
+     `deploy:log_revision` and `deploy:revert_release` now use 
`release_roles()` not `roles()` meaning that they
+     will only run on servers where the `no_release` property is not falsy. 
(@leehambley)
+   * Fixed bug when `deploy:cleanup` was executed twice by default (@kirs)
+   * Config location can now be changed with `deploy_config_path` and 
`stage_config_path` options (@seenmyfate)
+   * `no_release` option is now available (@seenmyfate)
+   * Raise an error if developer tries to define `:all` role, which is 
reserved (@kirs)
+   * `deploy:fallback` hook was added to add some custom behaviour on failed 
deploy (@seenmyfate)
+   * Correctly infer namespace in task enhancements (@seenmyfate)
+   * Add SHA to revision log (@blackxored)
+   * Allow configuration of multiple servers with same hostname but different 
ports (@rsslldnphy)
+   * Add command line option to control role filtering (@andytinycat)
+   * Make use of recent changes in Rake to over-ride the application name 
(@shime)
+   * Readme corrections (@nathanstitt)
+   * Allow roles to be fetched with a variable containing an array 
(@seenmyfate)
+   * Improve console (@jage)
+   * Add ability to filter tasks to specific servers (host filtering). 
(@andytinycat)
+   * Add a command line option to control role filter (`--roles`) 
(@andytinycat)
+   * Use an SCM object with a pluggable strategy (@coffeeaddict)
+
+-------------------------------------------------------------------

Old:
----
  capistrano-3.0.1.gem

New:
----
  capistrano-3.1.0.gem

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ rubygem-capistrano.spec ++++++
--- /var/tmp/diff_new_pack.nY8e0y/_old  2014-01-23 15:55:50.000000000 +0100
+++ /var/tmp/diff_new_pack.nY8e0y/_new  2014-01-23 15:55:50.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package rubygem-capistrano
 #
-# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -17,12 +17,12 @@
 
 
 Name:           rubygem-capistrano
-Version:        3.0.1
+Version:        3.1.0
 Release:        0
 %define mod_name capistrano
 %define mod_full_name %{mod_name}-%{version}
 %define mod_branch -%{version}
-%define mod_weight 30001
+%define mod_weight 30100
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  ruby-macros >= 1

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to