The revised XML is in my last post. It's really as simple as that: just
<maturity>1</maturity>
I think we're going to run in changes between the approved TIP and the implementation from time to time. It can happen when the TIP is incompletely specified, which we should fight hard against because incomplete specs usually go hand in hand with underestimated costs and consequences and delayed implementation. It can also happen when there are problems or obvious changes with the TIP that become apparent during implementation.
Here are two options on how to handle this:
- Changes must always be posted in the original TIP, and that posted changes are legitimate amendments if they are not vetoed within 1 week. Veto means that the original TIP must stand or be re-TIPped.
- Changes must always be posted in the original TIP, and must then be approved according to the same rules as TIPs - two yes and no no in a week, or full vote in two more weeks. Veto or negative vote means the original TIP stands or must be re-TIPped.
