Tickets :: [#11659] Bad version in git commit message after release

6.0.0-alpha12

6/16/25

Summary	Bad version in git commit message after release
Queue	Components
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	slusarz (at) horde (dot) org
Created	11/07/2012 (4604 days ago)
Due
Updated	11/07/2012 (4604 days ago)
Assigned
Resolved	11/07/2012 (4604 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/07/2012 05:21:55 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Resolved

11/07/2012 05:21:45 PM	Git Commit	Comment #3	Reply to this comment
Changes have been made in Git (master): commit 0e76932d93e3c2af55565049587aa07f5e524c12 Author: Jan Schneider <jan@horde.org> Date: Wed Nov 7 18:07:34 2012 +0100 [jan] Fix post-release incrementing of version numbers (~~Bug #11659~~). .../Components/Release/Task/CommitPostRelease.php \| 11 +++++++---- .../lib/Components/Release/Task/NextSentinel.php \| 11 ++++++++--- .../lib/Components/Release/Task/NextVersion.php \| 12 ++++++++---- components/package.xml \| 2 ++ .../Components/Release/Task/NextSentinelTest.php \| 2 +- 5 files changed, 26 insertions(+), 12 deletions(-) http://git.horde.org/horde-git/-/commit/0e76932d93e3c2af55565049587aa07f5e524c12

11/07/2012 04:16:06 AM	Michael Slusarz	Comment #2	Reply to this comment
Just released a FW_4 version and it does work there. So this is something broken on the master branch only.

11/07/2012 04:02:37 AM	Michael Slusarz	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Queue ⇒ Components Summary ⇒ Bad version in git commit message after release Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
After a PEAR package release (horde-components release), the git commit message has a version that is 0.0.1 points to high. E.g. Foo 1.1.1 package. Release is 1.1.1 New version (in package.xml) is 1.1.2 Commit message says "Development mode for Foo-1.1.3"