I considered releasing vegan3d together with vegan 2.2-0. However, this breaks API and can cause problems to packages depending on or importing from vegan. For instance, analogue of @gavinsimpson will fail because it imports ordirgl from vegan, but the function is now in vegan3d. Releasing vegan3d now would allow these other packages to adapt to the changes before vegan is released.
vegan3d duplicates vegan 2.0-10 functions (that will be removed from 2.2-0), but there is no technical nor practical problems with duplicating these functions.
I considered releasing vegan3d together with vegan 2.2-0. However, this breaks API and can cause problems to packages depending on or importing from vegan. For instance, analogue of @gavinsimpson will fail because it imports
ordirgl
from vegan, but the function is now in vegan3d. Releasing vegan3d now would allow these other packages to adapt to the changes before vegan is released.vegan3d duplicates vegan 2.0-10 functions (that will be removed from 2.2-0), but there is no technical nor practical problems with duplicating these functions.