upgrade_outgoing_qos seems not to work on inital publish after subscribe

[stefanbode]

If the option above is defined (true), this works not for the initial set of messages to publish after a subscription. E.g. all retained messages get published with q0. Only any additional change coming in later by a publish is uplifted in my example to q2 (QoS 2). This is working.

Is this a bug or is the intention to send the initial amount of messages only with a lower QoS?

log:

1503928837: Received PINGREQ from DVES_2DB1E1
1503928837: Sending PINGRESP to DVES_2DB1E1
1503928837: Received SUBSCRIBE from stbode_113852758
1503928837:     hm/status/# (QoS 2)
1503928837: stbode_113852758 2 hm/status/#
1503928837: Sending SUBACK to stbode_113852758
1503928837: Sending PUBLISH to stbode_113852758 (d0, q0, r1, m0, 'hm/status/ESP_001C0A/description', ... (21 bytes))
1503928837: Sending PUBLISH to stbode_113852758 (d0, q0, r1, m0, 'hm/status/ESP_001C0A/LWT', ... (6 bytes))
1503928837: Sending PUBLISH to stbode_113852758 (d0, q0, r1, m0, 'hm/status/ESP_001C0A/POWER2', ... (3 bytes))
1503928837: Sending PUBLISH to stbode_113852758 (d0, q0, r1, m0, 'hm/status/ESP_001C0A/POWER1', ... (3 bytes))
1503928837: Sending PUBLISH to stbode_113852758 (d0, q0, r1, m0, 'hm/status/ESP_001FD5/description', ... (13 bytes))
1503928837: Sending PUBLISH to stbode_113852758 (d0, q0, r1, m0, 'hm/status/ESP_001FD5/LWT', ... (6 bytes))

[PierreF]

It's a bug. It's now fixed on fixes branch and will be included in next release.