Re: components tool: CHANGED command
Jan Schneider <[email protected]> Thu, 09 May 2019 08:09:21 +0000
| Newsgroups | gmane.comp.horde.devel |
|---|---|
| Message-ID | <[email protected]> |
Zitat von Ralf Lang <[email protected]>: > Hallo, > > the git master version of the components tool seems to ignore both > CHANGES and package.xml when running the changed command. > Only changelog.yml is updated. > > While it makes sense to phase out CHANGES, I wonder if not updating the > history of package.xml is on purpose. > Maybe it happens somewhere later in the release process? Correct, it happens during the release now. There is no use to update three files at once, if two are only built from the first one anyway. Plus, it makes merging between branches harder. changelog.yml is supposed to be the same across all branches, while the correct versions are picked from it during release time. > The version shipped with git-tools seems to update package.xml and CHANGES. composer.lock could use an update probably. We don't use the update or release command of components in the git-tools though. -- Jan Schneider The Horde Project https://www.horde.org/ -- dev mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: [email protected]