PreambleThe current Milestone Criteria for OpenACS 5.0 has many criteria. Two of them stand out as still incomplete and still risky:
- Translation server data synchronized to branch
- all the core packages have upgrade scripts The upgrade script is actually a code-complete blocker - ie, we should not have produced the first alpha and begun alpha testing without having the 4.6.3 to 5.0 upgrade scripts for all core packages.
- "Tranlations" criterion for 5.0.0 is RELAXED/CONFIRMED
- "Upgrade" criterion for 5.0.0 is RELAXED/CONFIRMED
Purpose of this TIP
This TIP has two purposes. The first is to ask for a decision to defer or to not defer the two milestone criteria listed above. The second is to experiment with a non-binary TIP. I considered a "TIP + Amendments" process but that seems really complicated here. What I propose is that we skip "two yes and no no" and have a straight two-thirds vote on each of two decisions. After one week, we count responses. If a decision does not have a two thirds positive majority (and at least one vote), the status quo remains. In this case, the status quo is that the milestone criterion still applies. (More information on TIP process alternatives and Debian methodology)
OCT members must those vote in two parts, according to this template:
A relaxed vote means that we can produce OpenACS 5.0.0 release candidates and final releases without meeting the criterion.