Hey Remi,
I would love to update to buster. The current LAVA docs say stretch is the recommended release, though:
https://master.lavasoftware.org/static/docs/v2/installing_on_debian.html#str...
If you recommend updating to buster, this section should reflect this. For me personally, January 2020 would be okay.
Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg Direct: +49 40 791 899 - 183 Fax: +49 40 791899 - 39 tim.jaacks@garz-fricke.com www.garz-fricke.comhttp://www.garz-fricke.com/ WE MAKE IT YOURS! [cid:image001.jpg@01D5A36D.0881BA60] Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun
Von: Lava-users lava-users-bounces@lists.lavasoftware.org Im Auftrag von Remi Duraffort Gesendet: Donnerstag, 21. November 2019 14:55 An: lava-users lava-users@lists.lavasoftware.org Betreff: [Lava-users] RFC: when to drop stretch support?
Hello everyone,
Summary: We would like to drop the support for stretch in the (near) future.
Details: Currently lava-server and lava-dispatcher are supported on both debian stretch and debian buster.
Since LAVA 2019.11, the lava-server and lava-dispatcher docker images are based on debian buster and not stretch. Unittest are still running on stretch, buster and bullseye but integration tests (lavafed and meta-lava mainly) are using the docker container so they run only on buster.
Dropping the support for stretch will: * simplify testing * allow to use more recent version of python and django * remove some issues with old dependencies in stretch
But before dropping the support we need to ensure that users/admins had some time to migrate to buster or to docker-based installations.
In an ideal world, I would drop the support for stretch on the 1st of January 2020. But please answer to this mail so we can device of the right date all together.
Thanks
-- Rémi Duraffort LAVA Architect Linaro
