The milestones for the project need to be restructured. What originally gave rise to this was the discovery that the assumptions on which Milestone 2 of the original proposal were based turned out to be invalid. That milestone has required a great deal more analysis work than originally envisaged, and a very different implementation delivering it.
A divergence of views among the consortium on what Milestones 1 and 3 should deliver has also come to light. This has had a knock-on effect on the rest of the project. Hence all of the milestones are being re-scoped, reduced in number from 5 to 4. This has been agreed with all consortium members. The changes will be published to this repo as an updated proposal.
The milestones for the project need to be restructured. What originally gave rise to this was the discovery that the assumptions on which Milestone 2 of the original proposal were based turned out to be invalid. That milestone has required a great deal more analysis work than originally envisaged, and a very different implementation delivering it.
A divergence of views among the consortium on what Milestones 1 and 3 should deliver has also come to light. This has had a knock-on effect on the rest of the project. Hence all of the milestones are being re-scoped, reduced in number from 5 to 4. This has been agreed with all consortium members. The changes will be published to this repo as an updated proposal.