Second release candidate of Arduino 1.0.1 now available.

Community Suggestions for the Arduino Project
1

I just uploaded the second release candidate of Arduino 1.0.1:

Windows: http://files.arduino.cc/downloads/arduino-1.0.1-rc2-windows.zip
Mac OS X: http://files.arduino.cc/downloads/arduino-1.0.1-rc2-macosx.zip
Linux (32-bit): http://files.arduino.cc/downloads/arduino-1.0.1-rc2-linux.tgz
Linux (64-bit): http://files.arduino.cc/downloads/arduino-1.0.1-rc2-linux64.tgz
Source: http://files.arduino.cc/downloads/arduino-1.0.1-rc2-src.tar.gz

Please try it out and report any problems, either on the developers mailing list (http://mail.arduino.cc/mailman/listinfo/developers_arduino.cc) or the Google Code issue list (Google Code Archive - Long-term storage for Google Code Project Hosting.). I don't check the forums often, so I might miss problems reported here.

The main change from the first release candidate is the inclusion of more translations (~16 total) and the addition of a preference for selecting your desired language. Note that in Windows and some versions of Linux, the default language is based on the locale selected for the formatting of dates, times, and currencies instead of the language that your operating system shows up in. You can change the language selection in the preferences dialog box.

If you're interested in helping out with the translation process, see: Arduino Playground - LanguagesIDE. Comments about the translations themselves should be discussed on the translations mailing list, http://arduino.cc/mailman/listinfo/translations_arduino.cc. Suggestions about the internationalization process itself should be reported here or the Google Code list.

Thanks to everyone that contributed to the translation process!

Other things to try out include:

2

Issue 718 is still open, that one is mine, I see plenty more open ones from others

I don't get this development process, shouldn't the entire list be resolved before a release?

3

I don't get this development process, shouldn't the entire list be resolved before a release?

In most development processes (not only Arduino) the number of fixes per release is limited, otherwise one would develop endlessly as new issues keep coming in.

Then there is the matter of the seriousness/impact of issues, how hard does it fail? Issues vary from cosmetic to catastrophic (in all SW projects), and it makes sense to do the latter category first. Finally I think bugs reported that include a testable solution makes the most chance of being included.

Hopes this helps to understand development processes

Disclaimer: my opinion does not necessarily represent the opinion of the Arduino founders.