----- Original Message ----- > From: "Dennis Gilmore" <dennis@xxxxxxxx> > To: cloud@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Wednesday, December 4, 2013 6:13:40 PM > Subject: Re: Minutes from today's (12/04/2013) cloud WG meeting > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > El Wed, 4 Dec 2013 17:39:07 -0500 > Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> escribió: > > On Wed, Dec 04, 2013 at 04:16:25PM -0600, Dennis Gilmore wrote: > > > > * AGREED: cadence release to be monthly + trigger-based updates > > > > until we're more confident on automated testing (rbergeron) > > > So we are not going to be able to do this period. you will only be > > > able to release as Fedora itself releases. doing periodic updated > > > images can be doable, but we (with Release Engineering hat on) does > > > not have any ability to do what you mention here. the Best we can > > > do is to do > > > > So, what would it take to be able to do it? > > Well the Fedora release Cycle is what it is. I do not think you can > change that. I think that some of the wording used is poorly chosen. > > I think you are actually talking about updates images and not release > images. We have no way to determine how big an update set is so that > would be needed. something to monitor updates for security bugs to > trigger image creation. you need to assume we have no tooling to do > anything you want. so someone will need to write and maintain it. you > will also need to take your proposal to FESCo and have it signed off as > okay. Didn't spot propose something related to monthly pushes around the time that Flock took place? Seems like the rebuilds could occur simultaneously with pushes to reduce the burden of rebuilding images. That being said, we are still left in a position where it increases rel-eng load; not really sure how to avoid that other than having a group of people who are willing to help out. > > Dennis > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQIcBAEBAgAGBQJSn7ckAAoJEH7ltONmPFDRqxAP/2U60OAHXl1HWHwh3IwaXs2X > /1FedJ/7HGEFDRT4aMMD9rs2AarK5PB8lbhUeDwezeAc5y+RZWvkmBgNWumuCRGw > QnnUfZBzUPfVcAqc5zlCW9U3c/9uoWReVoTgqRusEgWPE5OZtZ2FSFrv9dxn1KV/ > Xv1CDomd2bw39FnFHiu79xUnER8tnNkz23YI6cbTBXFCU+Dx754xklDqyMcdQ+E4 > BJEkOa/cq5trlchYfw3DTYUlFpaeHUQg9ULkhNITsqG8AgwXfCykr7rWpz6WhcIn > S1SoX4HYB13Nxz76YrqFf73Phisa0uGybTHAIWhCJlHXFYuUWYQPUvOfNNZRmB4k > uKowi22Jrl9/3TbeAVlLMOQnTzEoDnFdx8j2Pr52HSsnmy3esn1yhc3j4mzh1yu6 > tOG2iqlpftkgvHEZmJP8Rkkj8QzaWjzA1NEBgsz20yYAe+h2PSn/H1Xo3GR9xqIv > mSCp8DKgB+uRPECP1dkDmzLoU9N/fU6rrIybMhxaEdmY77HwrZy0T21hPkIIE9jd > eyYaJv6+OP2GIriBRGkcfl8YCZTV9LZRd3sxcD26aPDn4gQ/0fAnDdJK8ul7nAac > EPgme8yriMuow+fnsbUYWC25ASDI8bE+wG7n5KVOwlxQjsm7D00XMOKWmHGGiuAe > 9M62Mr3o50ZjkNHlUui/ > =M/UD > -----END PGP SIGNATURE----- > _______________________________________________ > cloud mailing list > cloud@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
