Confirmed users, Bureaucrats and Sysops emeriti
419
edits
Global:1.9 Trunk 1.8 Branch Plan: Difference between revisions
Global:1.9 Trunk 1.8 Branch Plan (view source)
Revision as of 18:42, 13 December 2005
, 13 December 2005→A Dialog, or FAQ
| Line 87: | Line 87: | ||
A: Yes, and with module owner and peer review of the affected API-client files as usual. No one gets a free lunch on either side of an API, at the expense of the folks on the other side: | A: Yes, and with module owner and peer review of the affected API-client files as usual. No one gets a free lunch on either side of an API, at the expense of the folks on the other side: | ||
* If you change an API on the trunk, you need to keep the 1.8 branch of the #ifdef working (add the #ifdefs as needed, with review). | * If you change an API on the trunk, you need to keep the 1.8 branch of the #ifdef working (add the #ifdefs as needed, with review). | ||
* If you break an unfrozen API on the branch with drivers prior approval, you need to keep the trunk working too. | * If you break an unfrozen API on the branch with drivers' prior approval, you need to keep the trunk working too. | ||
This cost is a tax, and what you tax, you get less of. It should have the effect of minimizing, ordering, and rationalizing API changes so that we don't have too many, and so that no one gets stuck with his neighbor's tax bill. We will be developing a more detailed plan of action for API preservation and evolution, details TBD. | This cost is a tax, and what you tax, you get less of. It should have the effect of minimizing, ordering, and rationalizing API changes so that we don't have too many, and so that no one gets stuck with his neighbor's tax bill. We will be developing a more detailed plan of action for API preservation and evolution, details TBD. | ||