I'm assuming there is no issues with attaching your sitemap.xml to the root through the RSD 2.0 resources?
I could always FTP separately but I figure I might as well include it with the generated export files, if anyone knows.

Adding a sitemap.xml to the resources will work fine.

You can add it to your resources no problem however,,,
doing it that way means exporting your project with the site/page changes ,, then creating the new site map, then putting it back into RSD then exporting it again

I found that sometimes I would forget to put the updated version into the resources before exporting the project,, then remember later, which meant making a new site map, importing it to resources & then exporting the project again,, or ftp the new site map (which of course overwrites the existing site map, but then the old one is still residing in your resources in the RSD project, which if you forget again next time re-inerts the very out of date version. Not a great issue (except if they happen to crawl your site before you remember to update)
. I now find it easier to remember to update the sitemap if I place it into the site root directly, it sort of becomes second nature to do it that way,, but as I said it in't any issue to do it within RSD

OOPS INGER beat me to it

Thanks you never know, some software only allow certain extensions with attachments.
Yeah, that's a good point. I FTP it all anyway so at least having it in the root directory will remind me.

That's true, Wayan. I think I forget to update imported resources sometimes.

It would be nice if we had a 'live link' option that would always use the current version of an imported file in the resources.