The following is a list of questions (and, hopefully, answers) regarding the "Vancouver Prospectus", the proposal for Debian release management intended to take effect for etch (sarge+1), and assembled by the Debian release managers and archive administrators at a meeting in Vancouver, Canada in early March 2005.
- Why is the permitted number of buildds for an architecture restricted to 2 or 3?
- Three bodies (Security, System Administration, Release) are given independent veto power over the inclusion of an architecture.
- Does the entire team have to exercise this veto for it to be effective, or can one member of any team exercise this power effectively?
- Is the availability of an able and willing Debian Developer to join one of these teams for the express purpose of caring for a given architecture expected to mitigate concerns that would otherwise lead to a veto?
- How often can/should these bodies be petitioned for a reconsideration of their veto in light of underlying changes in circumstance?
- How will the exercise of a veto be communicated to the Project?
- The guidelines for eligibility as a released architectured, and for inclusion in SCC, could be initially met, but later fail. For example, an architecture could fall below the 98% up-to-date mark. Does this spell automatic expulsion from the slate of releasable architectures? Similarly, for how long are the petititions for inclusion in SCC (5 developers and 50 users) assumed to remain valid?