Hi all,

All v2.1.3 bugs currently have an assigned developer, I'm making the assumption 
now that these will be fixed soon, for a v2.1.3 release. If not, please do one 
(or more) of the following

1) Reassign / unassign your bug(s).

2) Move the bug(s) to a v2.3.0 target release.

3) Resolve the bug(s) (if it's either fixed or invalid).


Also, take a look at all bugs for v2.3.0, and make sure none of them has to go 
into v2.1.3 (and hence, v2.2.0).

Thanks!

-- Leif

Reply via email to