Hello Steve, Steve Conklin [2010-12-02 16:33 -0600]: > We've completed uploading kernels for the next cycle to our kernel ppa > and they've built. Now they need to be copied to the -proposed pocket so > we can begin verification next week. > > I'm not sure how the process is different now that we're doing it this > way instead of having you approve uploads before they are built. If you > can provide information about this it would help us.
Why are you now using a PPA instead of -proposed? A PPA shouldn't build a kernel any faster than the regular archive buildds? This approach effectively breaks the tools that we have for review, so the process for the person who reviews/accepts the upload will be a lot harder. That these kernels now may have security fixes and bug fixes intermixed is not a buildd/archive problem. The existing security update process already has a staging area and ensures that -proposed components aren't used, and for a "regular" SRU which goes to -updates the existing SRU process works just fine. However, mixing security and bug fixes IS a problem nevertheless: Either it means that we are holding back security fixes for two weeks, or that we smuggle non-security changes under the security fast-track to circumvent the -proposed testing and regression catching; neither of which sounds appropriate to me. > We've put the documentation we have here, there's a section titled > "Build PPA and process for pocket copying": > > https://wiki.ubuntu.com/Kernel/StableReleaseCadence > > Within that there's a link to this information written by Jamie > Strandboge: > > https://wiki.ubuntu.com/ArchiveAdministration#Copying%20PPA%20kernels% > 20to%20proposed > > Please correct anything that's not correct on those pages. I updated ArchiveAdministration to include the missing steps that are required for an SRU [1], including a disclaimer that this is in no way a sanctioned process. Thanks, and have a good weekend, Martin [1] https://wiki.ubuntu.com/ArchiveAdministration?action=diff&rev2=170&rev1=169 -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
-- technical-board mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/technical-board
