<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//DE"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><TITLE>Message</TITLE></HEAD><BODY>Hi,<br><br>i have been asked to upload osm2go to extras-testing. It's not quite clear to<br>me how this is actually supposed to work. I see several possibilities:<br><br>1) Just upload something. Others will do some testing and i can upload <br> a fixed version of they see problems. The new version will then go though<br> the same testing again. This is how i think it was initially meant to work.<br><br>2) Upload only things that have gone through my own testing to increase<br> the likeliness that it will go straight through testing without any problems.<br> This is the way i will use it.<br><br>I see several problems with 1):<br><br>- If something broken doesn't pass the tests and i keep uploading new<br> versions people will likely get tired of me and my perhaps perfect <br> version will stay in testing forever because nobody wants to test my<br> app over and over again<br><br>- If something broken actually passes the testing things get even worse<br> as a bug fix has to go through testing again and the broken version will<br> stay there until the bug fix passes testing<br><br>To me this means two things: <br><br>1) don't update too often, so people/testers don't get bored<br>2) put some extensive internal testing before promoting something<br> to extras-testing<br><br>This also means that i will delay the promotion of osm2go as i am currently <br>running my own tests.<br><br>I somehow think this is not the way it should work ... Any ideas how to use<br>it in a more efficient way?<br><br>Till<br><br><br></BODY></HTML>