On Wed, 2014-09-24 at 17:22 -0400, Christopher wrote: > > > That page only describes policy, it doesn't really connect policy to > actions one could take, or offer any explanation about what is actually > "frozen", and is very confusing. What can a package owner do in git? What > shouldn't they do? What about in Bodhi? (For instance, I have a trivial > update to a package sitting in F21 updates-testing, because I'm not sure if > moving it to stable would violate the freeze policy, but perhaps the git > commit it was built from was already an accidental violation of the freeze > policy?) As I mentioned, yes, the docs could do with clean-up and connection. The page which explains most of that stuff is https://fedoraproject.org/wiki/Updates_Policy . Basically I would like to have the schedule page, the 'branch freeze' page (whatever it winds up being called), the 'change deadline' page, the 'updates policy' page and the blocker / freeze exception SOP pages all link into each other and set each other up naturally so you can follow the whole process. I'm working on that right now, but got distracted by templat-izing the blocker and FE SOP pages so they don't get de-synchronized from each other. TEMPLATE ALL THE THINGS -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
