| 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/7/12 (4977 days ago) |
| Due | |
| Updated | 11/7/12 (4977 days ago) |
| Assigned | |
| Resolved | 11/7/12 (4977 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
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
something broken on the master branch only.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Components
Summary ⇒ Bad version in git commit message after release
Type ⇒ Bug
State ⇒ Unconfirmed
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"