constraints are not activate with argument

[rapidoo]

using Chronos on Ubuntu Ubuntu 12.04.2 LTS

chronos 2.3.4-1.0.183.ubuntu1404 amd64
mesos 0.23.0-1.0.ubuntu1204

When I use constraint without argument, mesos launch the job on the correct server.
But if I add << "arguments": [ "toto"], >> on the same job, constraint are not used, and the job is launch on any slaves.

{
"name": "fred",
"command": "/tmp/toto.sh",
<< "arguments": [ "toto"], >>
"shell": false,
"epsilon": "PT10M",
"executor": "",
"executorFlags": "",
"retries": 2,
"owner": "mail@machin.fr",
"ownerName": "",
"description": "",
"async": false,
"lastError": "",
"cpus": 0.1,
"disk": 256,
"mem": 128,
"disabled": false,
"softError": false,
"dataProcessingJobType": false,
"errorsSinceLastSuccess": 0,
"uris": [],
"environmentVariables": [],
"highPriority": false,
"runAsUser": "root",
"constraints": [
[
"role",
"EQUALS",
"alimentation"
]
],
"schedule": "R/2015-09-17T15:15:00.000Z/PT10S",
"scheduleTimeZone": "Europe/Paris"
}

[rapidoo]

I guess to problem is in JobUtils.scala

def getJobWithArguments(job: BaseJob, arguments: String): BaseJob = {

need to copy constraints too ...

[kapil-malik]

This is very important for us. Can anyone kindly confirm when 2.5.0 will be released. The fix at #562 works for us perfectly well, can someone please confirm by when it will atleast be merged in code base?