Revisions to version 1.03
The second decimal upgrade grade of the standard was proposed to occur during the spring of 2013, but faced delays that meant the timetable had to be revised. The process for doing so is outlined below.
You can contribute issues to be considered in future upgrades in the knowledge base.
|IATI||Community||Timescale||Due Date||Revised Date (final)|
|A clear cut off date for new submissions should be advertised.||Community submits and discusses proposals/ideas before the cut off date||7th Jan 2013|
|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||11th Jan|
|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)||25th Jan|
|These ideas need to then be built into fully implemented examples.||During this time the community can help shape the proposals||within 1 week||1 Feb|
|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||1 Mar|
|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||28 Mar|
|Consultation||over a 2 week period||23 Apr|
|Proposals are accepted, and implementation process begins.||23 Apr|
|Development version of changes are in place.||within 2 weeks||10 May||12 July|
|Development versions are available for community testing.||Community can test||for 4 weeks (increased by 2 weeks)||24 May||9 August|
|Bugs ironed out||within 2 weeks||7 June||23 August|
|Changes go live||21 June||6 September|