Hi, Il 23/09/18 09:38, Adrian Bunk ha scritto: > What is the version planned to be shipped in buster? > > 1.68 is already released, and 1.69 will be released in December. > > IMHO doing 1.62 -> 1.67 -> 1.68 would not make sense at this point. > > Better options would be: > 1.62 -> 1.68 -> 1.69 > 1.62 -> 1.68 > 1.62 -> 1.67 -> 1.69 > > The critical question here is whether there will be a transition to 1.69 > before the transition freeze (January 12th). I would suggest to avoid too much speculation on this point: uploading a new release to unstable is alone rather time consuming, because (beside the technical challenges of correctly installing dozens of binary packages) we have to fill a debian/copyright file for around 50k files with hundreds of contributors (this is why we were still stuck at 1.62). Since that would take time and doing the transition takes a lot of time too, I would just go for 1.67 at this point (for which at least the first step is already done), and once 1.67 is transitioned, see what can be done later. BTW, I am trying to do a rebuild of all packages depending on boost with 1.62 and with 1.67, to see which new build failures are introduced. I don't have much experience in mass rebuild and my only available hardware is my own laptop, so it might take some time. Giovanni. -- Giovanni Mascellani <g.mascellani@gmail.com> Postdoc researcher - Université Libre de Bruxelles
Attachment:
signature.asc
Description: OpenPGP digital signature