On Tue, Mar 2, 2010 at 12:39 AM, Simon Laws <[email protected]> wrote: > It feels like it's time we should have this conversation again now. > > From my point of view there have been quite a few changes in the > policy area. Still a bit more to do on matching but hoping to reach > that this week. > > We need to re-run the otests and see where we are. > > Can everyone comment again on what they need to do before we are in a > position to do a 2.0M5 release. > > I understand that there will be changes to the otests to catch up with > the specs that are going out for the next public review. I don't have > a feel for when those updates will take place though so we'll have to > take a view about waiting for them for M5 based on what else we have > outstanding. > > Regards > > Simon >
The two main things we've said would be in M5 were passing the otests for assembly, policy, java CAA and CI, and more completed distributed domain support. I ran all those otests yesterday and there are 26 tests failing. Most of the fails are related to policy though there are some others that look like regressions, I'll take a look at those this week so if you're hoping to reach the end of the policy matching this week thats all looking hopeful though given pass progress getting all 26 fixed in a week seems optimistic. Theres still some work to do in the distributed domain also and none of the distributed registries seem like they work completely in the scenarios we need so it would be good to try to get that done so i'll look at that too. ...ant
