| Summary | Test if package.xml is up-to-date on release |
| Queue | Components |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | jan (at) horde (dot) org |
| Created | 08/17/2011 (5068 days ago) |
| Due | |
| Updated | 10/11/2011 (5013 days ago) |
| Assigned | |
| Resolved | 10/11/2011 (5013 days ago) |
| Milestone | |
| Patch | No |
before a release. horde-components will error out in that case and
display the reason for the problem. Even if you run "horde-components
release" without "--pretend" the script will error out immediately and
do nothing.
In that case the problem can be resolved with a quick
"horde-components update --commit" which I wouldn't consider too much
of a burden.
So while this could be done as an interactive process during the
release I didn't see a compelling reason for the additional effort.
Check if the package.xml is up-to-date before releasing (
Request #10437)1 files changed, 20 insertions(+), 0 deletions(-)
http://git.horde.org/horde-git/-/commit/5bcf74afb6a84d3766ae5b99e99d2c4cbd81841c
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Components
Summary ⇒ Test if package.xml is up-to-date on release
Type ⇒ Enhancement
State ⇒ New
package.xml, show the diff to the user, and ask whether to apply this
change or keep going with release process.