One of the recent long threads on devel@ seems to boil down to two different possible interpretations of http://fedoraproject.org/wiki/Updates_Policy The differences were brought up in the context of the stable release policy but the overall question describes the whole document. One interpretation is that the goal of the update policy is to keep changes that need Fedora users to modify their behaviour (regressions causing loss of functionality, new UI forcing new workflows, ABI changes causing users to recompile applications that they've built locally, etc) from being pushed. As such, the policy outlines examples of changes that affect end users and thus should only be pushed at certain times in the release cycle. The other interpretation is that the policy describes specific types of changes that are highly discouraged as they can cause great disruption to a Fedora user's experience but things which are not specifically enumerated are fine.

I'd like to write a draft that clarifies this but I need to know which of those interpretations is the correct one for the current policy (or even each section of the current policy if it's decided that some sections were written with the idea of being examples while others were written with the idea of being a strict list of criteria) so that I don't change the meaning of the policy when I write the draft.