*Requirements project redux
*Session proposed by Chuck Short
*Thursday November  7, 2013  4:30pm -  5:10pm
*Design Summit 1
*Infrastructure

Now that we have gotten through a cycle with the  requirements project we should discuss what worked, what didnt work, and  how things can be improved.

	* How we got here
	* What happened this cycle:
		* What went wrong - pain points
		* What went right - automated synchronizatoin amongst the projects

What we should do:
	* formally document the process in the openstack wiki if not already done so
	* Better communication and tracking of new dependencies for openstack
	* Better tracking (maybe a bug report should be opened against the project)
	* Other dependency requirements: 
		* Security history of the dependency that is going to be added (Open/closed CVE)
		* Testsuites that is incuded.
		* When was the last time the package update on pypy
		* Dependencies should be included as well for review
	* carry on

Current requirements for python dependency:
	* Packaged already  in Ubuntu/Debian/Fedora
	* Python3 compatible
	* ???

Release management consequences:
	* Discuss requirements capping for stable branches
	* Requirements freeze around release time

Freeze Policy
	* requirements master branch is frozen (think temporary -2 reviews) at feature freeze
	* It remains frozen until all projects reach RC1 stage (should take a few weeks, not a few days or a few months)
	* When all projects have published their RC1 we cut a milestone-proposed branch for requirements
	* That branch gets migrated to stable/* as all branches do

TODO:
More involvement in requirements project reviews from distros (Ubuntu+).
Add requirements criteria acceptance documentation to repository (HACKING.txt)
Automated check as part of gerrit reviews to pickup transient dependenies during review
Minimum version review and checks