I've just updated the next milestone of pyDAL to be 15.05 instead of 15.04, but I would prefer these steps:
1) craft a web2py 2.11 alpha or beta to selected users since we never tested py3 changes on existing py2 applications. These users should check if everything is ok with next pyDAL
2) select all the missing issues for pyDAL 15.05 and close 'em all before the 15th of May.
3) release pyDAL 15.05 on the 15th of May (or before if we're ready..)
4) if point 1 was ok, release web2py 2.11 stable with pyDAL 15.05
/Giovanni