LS,

When I seeing once again our release schedule shift, I think we have
no option but to move feature freeze for the next release forward.
This is the only way it seems we can reduce the complexity of the
total sum of changes. Therefore it is the only way we can prevent
lapsing even more in time without risking reduced quality of our next
release.
So I propose to move feature freeze forward by a month to be at the
19th of June (instead of July). I don't think we need to strictly move
code freeze forward as well but vigilance onto added features will be
necessary.

-- 
Daan

Reply via email to