There's something of a changelog for the hardware here: http://www.arduino.cc/en/Main/Boards, though it doesn't yet have any links to more information about each version.

Tim O'Reilly asks about the equivalent of a version control system for hardware: http://www.itconversations.com//clip.php?showid=716&start=23:04&stop=23:38 (full talk here: http://www.itconversations.com/shows/detail716.html)

It seems to me that there's also a need for simpler ways to create and extend PCBs/hardware designs in general.  Eagle is cool (and free), but still very complex for someone who just needs to make a few changes.  Are there better ways?

You can also use an ISP to update the 8U2 firmware, if you have one.

According to the USB folks, we're not really allowed to share our VID / PIDs with other organizations.  So the firmware was modified to use other ones.  Probably we should create a different version of the .inf file that uses the other VID/PID pair.  The intent is that any VID/PID pair should work with the IDE, but that the Arduino ones should only be used with the official Arduino hardware.

Thanks ant.b.  I was supposed to write a tutorial like this one but didn't get to it yet.  I linked here from the Arduino Uno page (under the programming section).

You have to worry about power dissipation as well as current.  Here's what Gianluca has to say: "With 150mA of load at 12V the regulator will go in thermal shut down (or burn) because it will dissipate 1.3W instead of the 0.45W it could not exceed without a proper heat sink

At  12V it could easily provide 50mA (75mA @ 9V)

it is the same for the Mega2560"

Yeah, I realized my post was a bit Mac centric.  In OS X, there's an explicit UI difference between closing a window and quitting an application.  Most applications remain running even after you close the last window, so the two actions feel separate.  I think the latest versions of Processing will stay running after the last window closes (which I'm planning to port over to Arduino).

On Linux and Windows, though, I realize this distinction doesn't really make sense and so the current behavior is confusing and should be changed.

I'm not sure I'm entirely clear on the supposed bug here.  If you quit (File > Quit or Control-Q), the IDE should save and restore the sketches you have open, along with their location and position.  I just tried with 0021 on Mac OS X and it seems to work.  Is this broken on other OSes?

If you close the last window, the Arduino IDE will also quit.  In this case, when you relaunch it, it won't restore the sketches you had open, because there weren't any.  It will create a new blank sketch in the default location.  Is that the behavior people are objecting to?

As I understand it from Gianluca, the actual silkscreen file is sent directly to the photosetter, since it wasn't able to process a Gerber of the desired complexity.  That is, there isn't an alternative Eagle file with the actual silkscreen, so I believe the reference design is the one used to produce the boards (although it's possible for it to get slightly out of sync).

New picture is up.  You might have to hit reload.  Let me know if I missed any copies of it.

I've asked someone to take a new picture.  I hope we can get one up soon.

Ah...  hex file download is something that could be nice, but never seems like a high priority.  If you're already using another tool to generate the .hex file, why upload it with Arduino?

Uploading using a programmer (from within the IDE without editing any preferences files) is in the plans for 1.0: http://code.google.com/p/arduino/issues/detail?id=260&start=100

In the standard distribution, we only include support for processors that are on an official Arduino board.  However, people have made cores that run on the ATtiny85, and it's possible to install these separately: http://arduino.cc/en/Guide/Environment#thirdpartyhardware

It's possible to upload a sketch using a programmer, but this currently requires modifying your configuration files.  We'll be including support for it directly in the IDE in the future: http://code.google.com/p/arduino/issues/detail?id=260&start=100

The preliminary issue list for Arduino 1.0 is up on the Google Code site: http://code.google.com/p/arduino/issues/list?q=milestone=1.0

If there's something I missed, consider opening an issue for it.  The forum is a good place for discussion, but things tend to get lost here.