Version 18.3 in Buster

Version 19.2 in Sid/Testing

Microsoft asked me how we can get 19.2 in Buster.
Question: what feature in 19.2 is needed?
We need the info to convince the release team...


zigo - voluneteer to work
old version is good enough for OpenStack
qemu guest agent in generic image

process to upload to stable
it has much bigger impact than agents - Release Team might be more hesistant
to allow it
No known history of breaking by new versions

AWS does not need it per se - but new version might change something
They'll want to test it

If more people (cloud users and providers) will contact Release Team that
new cloud-init is needed *and well tested*, they might have more reasons to allow

new CI job to build images with new cloud-init, and test it
test on unstable or stable?
we'll need to test both next year, when Python 3.8 will land in unstable
while Buster will have 3.7

How to get cloud-init? unstable with pinning?
our own repository? We'll need to test explicitly version which we'll want
to have uploaded to stable
apt repository in gitlab (salsa)?
(potential ToDo of waldi)