 Hello, great welcome back. Emilia will be telling us about the release team and what you can do to help to make the stretch release possible Thank you Okay, so Yes, my name is Emilia. I'm release manager for stretch together with nails. What's in there? I'm going to be talking about how can you help make the stretch the stretch release possible How can you make how can you help make the the freeze shorter than usual? and I'll tell you a little bit about the procedures the new changes in the in the freeze policy and And some surprises at the end Okay, so first of all, let's start with the with the release team As I said Nils and myself are the release managers Then there's Adam Julian and Philippe taking care of stable and Andrea Cyril Felipe Evo, Jonathan and Mehdi are release assistants So we work as a team every everyone can take care of anything But the stable release managers and the release managers have the last worry if there's any controversy or any hard decision to make If you want to join come tell us We're always looking for people to help with with all the work that we do with the with the tools that we use So we get in touch if you're interested Now let's look at the timeline for for stretch The freeze was going to be the fifth of November back, but we pushed it back two months So on November the fifth we're going to stop accepting new Transitions if you have any transitions plan, please let us know especially if they are big As the deadline is isn't it's very very near Then on December on December the fifth We will stop ignoring we will start ignoring Urgencies so all packages will need 10 days to migrate to testing if if for some reason your package needs to migrate sooner than that perhaps because of a Security fix then let us know you can write as an email or something and And we'll we'll push it We will also take a final look at the architectures for stretch We See if any problems can come up and we need to drop an architecture or something, but hopefully It will all be fine and on January the fifth there will be we will have the soft freeze So from that point on no new packages will enter testing Updates can still go in but then if you have a new package planned You need to get it in Testing before that which means you should upload it ten days before that and plan for any possible release critical bags so get it in there soon also also be aware of You should be aware of auto removals so your package can be removed from testing be careful with that because if it gets removed It won't come back in and Then on February the fifth is the heart freeze from this point on You will need to request an unblock if you have any updates to your packages for backfixes or anything as usual and Hopefully not too long after that we will release and we can party and drink and enjoy So winter is coming and the freeze is coming with it and I'm gonna tell you something I hope that this isn't the longest winter in history second Yeah, well Yeah, hopefully it won't be it won't last too long Now let's talk about the DRC bags Okay, maybe not that kind of RC bags But I release critical bags. We have over a thousand bags right now affecting testing according to UDD of Those 300 bags were recently filled for the GCCC transition And another 300 were filled for the the helper compatibility deprecations But only about 300 are affecting key packages. This is a very nice number The other 700 are affecting packages that can't be removed from testing if they Don't get fixed if the maintainer doesn't react or anything. So So it'd be nice if they are fixed But if they're not they won't block the release. However, these 300 release critical bags These are the ones we we really need to look at This is the graph of the of the release critical bags This is the point when of the Jesse release and the freeze I think was Around here right November yeah, so So as you can see the number of release critical bags was was about the same before the freeze except for this Which is Which is this to this is the that help her compatibility Release critical bags and this is this is six But then in a month from now that the auto removals will start removing those and it will go down again So fix your package if you don't want to remove We have a problem with unstable so many bags there I think we should start out auto removing packages from there, but that's That's a discussion for another day and The peaks in in this is stable this picks this pick and this pick are because Whoever feel those release critical bags use their own tax, but that's fixed so Now auto removals Okay, maybe maybe not this kind Or maybe we will remove your car like this if you don't fix your bags We'll see yeah, so auto removals help a help a lot as you as you can see we don't have Numbers right now because we just realized that we haven't been keeping the the data in a machine possible way But us but we will fix that for for next year, but they help and you have probably seen many many packages being removed and And the difference here between testing and unstable Is because of that in a big way So we will keep removing packages from testing even during the freeze And packages that get removed won't reenter so be careful now transitions Transitions are being very smooth Thanks to some changes that we have implemented this cycle like and Craft is ignored for testing migration. This helps transitions because When you rename the library the old library doesn't need to be removed for the for the new version to migrate Which means the transition can can move to testing very quickly and then it can be finished a bit later This also means we can we can start another transition before the first one finishes if they even if they If they collide So we are accepting transitions very quickly Usually in less than a day As long as you provide the necessary information like you Tested the reverse dependencies and everything and you come with us with that information So there's no reason not to not to report a transition back and wait for wait for for the goal So please do that especially for with big transitions so we can avoid the collisions and The freeze is coming for transitions in November as you saw so please If you want to if you have a transition to make Planet file about whatever Yeah smooth transitions and maybe not that smooth but So How to how to make a transition and the ideal way you upload your page to experimental to clear the new queue to go through new and then You get a Transition tracker auto-generated. You don't need to ask anybody. It's very nice There we can see if there are collisions with other ongoing transitions or with other plant transitions or or anything the second step and make sure And your package builds if it doesn't build you need to fix that before the transition can start and Rebuild your reverse dependencies. This is one of the the things that people forget about or that people Maybe people are lazy and don't want to do it, but it is the biggest Biggest the most important thing we build your reverse dependencies and and check that they if they need and Changes for for your API changes or or patches or anything or if they just it can be rebuilt after the transition starts and then report a bag for the transition and You could upload it directly if it's a very small transition Maybe a couple of packages that you maintain and that you can take care of yourself Use your judgment, but if it's have if your library has you devs then please Check with the beyond release and the beyond boot as it can affect a devian installer release So propose updates for stable and all stable. I'm gonna quickly remind you about the procedure It's very important that I mean the bags that you want to fix in stable must be fixed in a stable Sometimes the bags are fixed but people The bts doesn't have the the right information. So we we get confused And the stable release managers get a bit grumpy. So so make sure the bts has the information so so we can just So we don't have to ask about that And then report a bag and you should include a justification why you have to fix why it's important to fix this bag Tell us about the back numbers that you are fixing and under severity is a change log entry and a source depth if not a binary depth if but the source one between stable or stable security and and your and your your proposed update and Wait for a knack before you upload this to stable Now the first policy for stretch. We have making a few changes I Don't think this is updated yet, but we will we will push it very soon The the freezes guy is going to be grad grad as you saw and In the freeze we will accept the fixes for release critical bags also for important bags and Always be unstable not propose updates and Translation updates or documentation fixes And There won't be a automatic and blocks. So if you upload your package two days before the freeze It won't get an automatic exception. It will have to request an unblock So it will be easier if you upload it Ahead of time, you know, so it migrates before the freeze. But if not, you can request an unblock But about auto removals one change is That they cannot remigrate if your package gets gets auto removed During the freeze there won't be an exception for it This is a change from the Jesse release So don't assume any packages safe from removal because we might remove it before the the auto remover Kick scene if it's a blocking some something else or whatever Don't wait till the last day to fix to fix the the package Unblock request this is important for the for the freeze Please report a bag Don't come on IRC and say hey, I want to fix this back Can I do you think this is sensible instead of asking on IRC just ask on on a bag report? And you should always include the justification for why this update What bags you are fixing and they source the beef between testing and your proposed update Or your update? There's no need for pre-approval We trust your judgment that you will upload and Sensible stuff, right? So you can go ahead and upload to unstable and after that you can wait a few days If you want make sure it builds everywhere there No, new release. No new bad reports are reported about the Christians and then request the unblock The the pre-approval Waste is our time because we have to look it ahead of it then later when when you upload So well if you are really unsure about something you can ask but if you think it's right Then you can go ahead so architecture for stretch We have The x86 the arms mix and mix cell power PC64 little indian and s390 this we're already in Jesse Meep 64 year is a candidate and I Think this morning the last package that needed a rebuild was fixed. We have the dsa hardware It's in the main in the main archive. So we are going to boot Strabid in testing very soon So it's very likely that it will be released in stretch And we have concerns about our power PC and free BSD These are concerns about the manpower the the number of porter the porters basically so if you Are interested in seeing any of these or you are a porter and Want to support this and we'll be working on this we will have a Call for porters very soon. So please reply to that and let us know so we can we can make a decision about that now for stretch and We expect to ship Linux for 10. This is the reason that we delayed the The freeze because the fourth and release is going to be LTS Otherwise by the time if we shipped with the with the kernel from From November or October By the time of their release it could be almost end of life We will also have GCC 6 6.3 Python 2.7 didn't change of course, but 3.5 Paralysis expected to be 524 we have 522 right now, but we have a transition plant and You know 222 and KDE 16 o'clock second 322, that's right my bad You know people don't like you know three so We're going back Now how can you help? Obviously if you upload something to Unstable that isn't meant for for the release during the freeze that disrupts many things Especially if your package has reverse dependencies if it's a library, so don't do that don't introduce new transitions Don't upload things that you don't mean for stretch to unstable. You can use experimental. I know experimental isn't picked up by default and all of that but the freeze should be Should be short. We hope we hope that it will be short. So So if you do that that will help that will help us So packages don't have to go through proposed updates Fix really is critical bars. The list is there as you saw The sooner we fix them the sooner we release so so we need that Especially those affecting key packages the other ones It's nice to fix them. But if we don't fix them packages can be removed so And you can organize or participate in a box question party Also, we need people testing the upgrade from Jesse to stretch And the installation process new installs Please do that if you can and report Any problems that you find or successes for the installation process as As it's usual and to the respective packages If you if you have something important for the release notes your package has something some important change That should be mentioned you can file a bag with some explanation So it can be included and If you need something from the release team like a bean and bean and you Or something don't don't leave a note on on on your Package by report. I hope that we see it come to us file a by report against released at the end of tour So we so we don't miss it and then we can act on it Now how to contact us is if you need if you need any things I Report report back released at the end of tour for anything that we handle through Through the back tracker. This is important. So so we don't miss it if you send an email We are going to be flooded by by by emails during the freeze with With a block request and so many things if you send an email. It's very easy for it to be missed So file a back report For other things you can you can contact us on the on the mailing list Send us an email and we'll help you again, please by report people People forget about this people come on IRC and ask Can I have this transition? Can you can you been in and you this package? It's it's better if you file a by report You can also come on yours come on IRC for for other things or if you need a live discussion about something and report back please and finally So you know stretch plus one is going to be bastard Bastard plus one We'll be bullseye. I want to thank Debian and Collabora for bringing me here If you have any questions, please go ahead About Debian or Game of Thrones or whatever. How did MIPS end up as a release architecture as a big and Was the question again, how did it end as a release architecture? Yes Well, there's a lot of hardware there. There were people porting it and so on so so it became one and As long as it keeps being supported upstream and we have porters and there's hardware There's no reason to drop it. Of course, if if upstream support falls falls apart I think there were problems with With a Lipsey or the kernel answer if problems come up We might drop it at some point and that's possibly That will happen in the future at some point, but it's not happening for stretch We will see how they go in the future Question from IRC Could you elaborate a bit on the reasons for? disallowing re-entry of auto-remove packages In particular if the auto-remove package is a build dependency of something else that would otherwise qualify for the release Right or greedy yourself Yeah, so So if it's a build dependency That's that's basically the same thing All packages in the chain will are notified by the I believe by the auto-remove all tool If not, let us know and we will fix that but If if if one of your dependencies have a bug report and it doesn't get fixed And your package gets removed I mean There's nothing preventing preventing the maintainer of these packets to fix the other one so or or to Being people or or if this happens and you cannot fix it and whatever you can come and let us know and we might Give an exception in this specific case, but But in principle if it gets removed then it's removed so Hello, apparently we have users for power pc 32 bits big Indian people still using this Maybe this is more a question for power pc porters if they would be willing to switch to switch the 64-bit big Indian user land right Yeah, that's something I want to look to take a look at whether The power pc 32 bit in the power pc hardware can run on ppc 64 or not and make sure Check whether we have porters check with the ppc 64 porters and then we will need to make a decision but It's clear we have users of power pc So so we need to support which we would like to support them one way or another or another Whether it's through power pc 32 bits or through ppc 64 bsa recently received an offer for Spark 64 hardware directly from the hardware vendor When do you expect at the latest point to include a new architecture in Release time frame into streets. Yes. Yeah, that should happen As soon as I mean, yeah, I mean, I mean we haven't we haven't heard anything about the spark system for porters I think there was an email on the on their qualification thread, but We didn't get any direct Email telling us that they want to include it Okay, we can talk later, but if you want an architecture in stretch The things that need to happen are that the hardware needs to be Maintained by dsa, which you said you have an offer the port needs to be in the main archive and then we can We can think if we can see if it can be added testing. So I'm missing something in in practice It's the 4th of July August September October November 12 weeks Probably pushing a lot for stretch even if we had a hard way tomorrow Yeah, I saw that the the number of packages was very high like 11,000 out of the 12,000 that currently at 10,800 binary arch packages on spark 64 One guy recently James Clark. I don't know if he's here He's just a Debian maintainer, but he actually fixed a huge load of packages As for upstream oracles actually paying lots of Developers now to to support Linux on spark. They have their own distribution, but they are also like doing lots of upstream work and At some point oracle said that they would be willing to donate hardware to Debian and that would be at least one Hopefully to spark m7 servers which run at like 40,000 grand 40 grand One server that was that 32 core machines Right, that's more or less the fastest you can get with spark. Yes So send us an email maybe include the dsa team and you have to be masters. Yeah, dsas is in the loop So yeah, just just a matter of like oracle like, you know Yeah, it's moving they're like they're a huge company and they take forever to yeah But let us know so we can know about this plan and and see if it's possible for stretch if things move on and Until as they'll tell you the requirements that we have But defeat if it happens and everything looks fine then I think we'll be happy to include it And I just finished setting up the spark 64 potter boxes someone wants to try okay It's called not good that Debian dot that Okay, any more questions Not so much a question, but a comment. We're already planning for some BSPs in the UK We're gonna have to find more stuff to do because you've done the auto removals Well, there's still 300 release critical bars, so hopefully you have some stuff to do But they take a lot longer to actually fix You cannot just remove those sure so obviously It's great if other people want to do BSPs, too We're we're gonna work or Jonathan and I are arguing up who gets to host in the UK. We might do both of this You can do too we won in Germany and I think in the end of September beginning of October I have an additional question which more or less goes directly to Steve Do we have an expectation on when the release candidates for the Debian installers will fit into those time frame? To be honest, that's up to Kibbe We just released Di alpha 7 in fact he announced it was it last night early this morning I think we're probably ready to start calling them beaters any time Unless anyone has major things they want to put into di You know we're calling them alpha so far because we haven't started getting close to a release Yeah, we're ready to go. I think Speaking about bed as in for DI. How's it progressing on the artwork front? so We sent out a proposal or a request for it, and I haven't heard back from anybody yet Unfortunately, I think somebody created a bigger page for a single artwork, but nobody actually Showed up on there and said I'm doing artwork So we're still looking for people to do that and announce it So there's one person who's created some artwork and it's on a wiki page and they haven't really talked to anyone though anything else Okay, thank you very much See you fixing bags in the frizz