Fri, 10 Apr 2026 17:52:45 +0000 https://bugs.horde.org/ticket/10437 Test if package.xml is up-to-date on release When doing a release, check if an "update" command would change package.xml, show the diff to the user, and ask whether to apply this change or keep going with release process. Wed, 17 Aug 2011 20:30:18 +0000 https://bugs.horde.org/ticket/10437#t67025 Changes have been made in Git for this ticket: 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 Tue, 11 Oct 2011 08:09:30 +0000 https://bugs.horde.org/ticket/10437#t68091 > When doing a release, check if an "update" command would change > package.xml, Done. > show the diff to the user, Done. > and ask whether to apply this change or keep going with release process. I would expect the user to run "horde-components release --pretend" 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. Tue, 11 Oct 2011 08:20:31 +0000 https://bugs.horde.org/ticket/10437#t68095