The issue queue for <a href="http://drupal.org/project/xmlsitemap">http://drupal.org/project/xmlsitemap</a> is over there.<br><br>Instructions for creating patches are at <a href="http://drupal.org/patch/create">http://drupal.org/patch/create</a><br>
<br>Development tarballs are created automatically by the Drupal.org packaging script and have big red Xs next to them to stop regular users downloading them. It's the same as checking it out from CVS, except a daily snapshot of whatever's in there at the time. <br>
<br>Development tarballs are for people to try out and contribute back bug reports and patches back to the issue queue so they can be rolled into the next stable release - if you can fix things locally, you could have spent the time doing this instead of sending a complaint to however many thousand people subscribe to this list.<br>
<br>Nat<br><br><div class="gmail_quote">On Thu, Dec 18, 2008 at 12:47 PM, Jens Reinemuth <span dir="ltr"></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi everybody...<br>
<br>
since a couple of weeks i have permanent problems with the development<br>
snapshots of the XML Sitemap.<br>
<br>
O.K. i know these are dev-snapshots, but i don't really uderstand what<br>
happens here. if i would check out these files from CVS, i could live<br>
with the recent bugs (nearly all are typos, e.g. "columhn_exist" or<br>
forgotten semicolons, paranthesis, ...) but i really wonder how someone<br>
could package these broken files into a tar.gz and release it...<br>
<br>
This is very uncomfortable on my development servers as they nearly all<br>
run on lighttpd and you have to do some tricks to get it to work with<br>
drupals Clean-URLs, you allways have to change same line of code in<br>
settings-file, run the updates, get errors, fix all the stupid little<br>
typos, run updates again, add semikolon, ...<br>
<br>
I really would see the devs checking the code (or simply use something<br>
like eclipse and look for the underlined parts of their code...) before<br>
packaging it and releasing it to the website.<br>
<br>
On all my servers there are about 15 drupal-Sites and i never had these<br>
problems with any other modules.<br>
<br>
Jens<br>
<font color="#888888"><br>
--<br>
Jens Reinemuth<br>
Ahornweg 23<br>
51469 Bergisch Gladbach<br>
Germany<br>
</font></blockquote></div><br>