Recipe builds should have debianized tree built previous to building the source package

I wonder whether it's necessary at all to perform the source build in a virtual machine running the same series that will be used for the binary build. Wouldn't it be possible to always use Maverick (or the development version of Ubuntu in general) for building the source package? This would ensures access to the latest version of bzr-builder, while the binary build will be performed using the appropriate Ubuntu series.

bzr-builder provides a --distribution parameter that can be used to set the series entry in debian/changelog to the appropriate value.

The other two options I can think of is adding bzr-builder to the Dapper, Hardy and Jaunty repositories or simply not listing Dapper, Hardy and Jaunty as possible build targets when the user requests builds, where the later option is certainly not desirable.

Building everything on the latest release would work in 99% of cases, but we decided
to build on the target distroseries to get the extra 1%, at the expense of having to provide
backports of bzr-builder.

Thanks,

James

Thanks for your answer. So the bug description could be changed to indicate that bzr-builder has not yet been ported back to Hardy and Jaunty, I guess.