Decimal Upgrade to 1.02
The first decimal upgrade of the standard happened in December 2012. The process for achieving that is outlined below.
Details about the specific changes are listed on the knowledge base in the First Decimal Upgrade Forum.
Full proposals were worked up on the Changes Specification page of the wiki.
IATI |
Community |
Timescale |
Due Date |
|---|---|---|---|
| A clear cut off date for new submissions should be advertised. | Community submits and discusses proposals/ideas before the cut off date | 1 Jun | |
| The TAG technical team should have agreed as to which proposals should go forward to the next upgrade, and communicated this with the community. | These are flagged on the knowledge base as under consideration. During this time the community can help shape the proposals, and discuss what has been included or left out. | usually within 1 week | 6 Aug |
| Consultation | During this time the community can help shape the proposals, and discuss what has been included or left out. | Over a two week period (three weeks during Summer) | 31 Aug |
| These ideas need to then be built into fully implemented examples. | During this time the community can help shape the proposals | within 1 week | 7 Sept |
| At which point they are published as proposed changes for consultation | During this time the community can help shape the proposals | over a 4 week period | 28 Sept |
| Final proposals are published. | At this stage we hope that the proposals are solid and will be accepted, but people will still have a chance to air their views. | within 2 weeks | 12 Oct |
| Consultation | over a 2 week period | 26 Oct | |
| Proposals are accepted, and implementation process begins. | 29 Oct | ||
| Development version of changes are in place. | within 2 weeks | 9 Nov | |
| Development versions are available for community testing. | Community can test | within 2 weeks | 23 Nov |
| Bugs ironed out | within 2 weeks | 3 Dec | |
| Changes go live | 17 Dec |