[Tickets #10437] Re: Test if package.xml is up-to-date on release

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10437
------------------------------------------------------------------------------
  Ticket             | 10437
  Updated By         | Gunnar Wrobel <wrobel at pardus.de>
  Summary            | Test if package.xml is up-to-date on release
  Queue              | Components
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Gunnar Wrobel <wrobel at pardus.de> (2011-10-11 08:20) wrote:

> 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.