Actions
Bug #3560
closedScala-ldap version is not up to date
Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
Architecture - Dependencies
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Scala version has not changed with the upgrade of 2.4 version when we make a release :
We have release 2.4.4 for a long time but scala ldap parent version is still 2.4.4-SNAPSHOT
- There is no 2.4.4 tag
- the parent version should have change to 2.4.5-SNAPSHOT
Updated by Matthieu CERDA over 11 years ago
- Status changed from New to Discussion
- Assignee set to Jonathan CLARKE
- Priority changed from N/A to 2
This looks like an oversight during the release, as the packaging part looks correct to me...
I do not think this is a bug but more a human error...
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.5 to 2.4.6
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.6 to 2.4.7
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.7 to 2.4.8
Updated by Nicolas PERRON over 11 years ago
- Status changed from Discussion to Pending technical review
- Target version changed from 2.4.8 to 2.4.7
- % Done changed from 0 to 100
This error was due to a bug in our automatic scripts. This has been repaired during the 2.4.7 release
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON over 11 years ago
This bug has been fixed in Rudder 2.4.7, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000041.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog24
- Download information: http://www.rudder-project.org/foswiki/Download/
Actions