Is there a schedule for 1.0? I thought I remember someone mentioning June. Will there be any beta testing?
Yes !
I really also would like to get some orientation what's going on.
It's a long time silence already. Thanks
I got the impression that 1.0 would be a ways away, a year or more? I think there will be a V19 or even 20 released before 1.0, but maybe I am wrong on that.
Lefty
It would be nce if we were privy to the plan? I understand the principle of it is done when its done. but without timelines goals are seldom met.
I understand the principle of it is done when its done. but without timelines goals are seldom met.
I've always assumed that open source projects are run a lot different then commercial projects, so timelines might not even be in the mix. In the mean time the exisiting IDE updates have been pretty frequent. Is there some specific feature you are waiting on?
Lefty
It would be nce if we were privy to the plan?
Join the developers mailing list... you will know what is happening. Instructions for joining are somewhere in the wiki.
I thought that the 1.0 was coming out in June. I expect to release a product in about 6 weeks. While release 18 is working very well. My boss and our customer would be nervous if they knew thier product was developed on alpha or beta ware.. I will likely install the hex files without the boot loader if 1.0 isn't released yet.
If that is the case, you should not be relying on an opensource platform to be developing your project. It is constantly evolving and not guaranteed to provide you with anything.
That being said, the bootloader is completely independent of the Arduino IDE. It would be useless to bypass the bootloader because the IDE is not classified as a final release.
Ray,
Not to be too harsh, but your comment makes little sense,
especially the part of removing the bootloader.
Of all the components in the "arduino" development environment, the
bootloader code is probably one of the the most stable. It is a very small amount of code and is actually a single module.
Go back through the diffs in the SVN tree. There have been very few changes to the code in 3 years. Sure some minor updates here and there and support for certain new MCUs was added but the mainline logic and more importantly the command/message interface has not been altered.
So of all the things to be concerned about and to avoid or leave out, my opinion is that the bootloader should not be one of them. Also keep in mind that if you remove the bootloader, you will need to use an ISP programmer to update the code rather than be able to use the serial interface.
The rest of all the arduino code is all open source. You have access to it and can see all of it.
From bootloader code to the core code to the libraries.
The IDE should not be a factor as none of it is in a build image. (HEX file).
Why should it matter if the Arduino toolset code is "1.0" or not?
What matters the most is does the created image work/function properly?
and can you re-create your production code on different machines in case something happens to one of them?
If you are worried about tools, then grab a full snapshot of the build 0018 toolset from the SVN tree and archive it away so that you can build,update, or modify your toolset if you ever needed to.
And taking a step further, what about the underlying gcc toolset?
What does "alpha", "beta", or an "official"/"production" release of gcc mean?
The gcc toolset that Arduino uses is not from the official gcc sources.
For Windows, Arduino supplies a pre-built version of the WinAVR avr-gcc toolset.
This gcc toolset is behind the official gcc repository and contains many patches that are not in or even sanctioned by the official gcc repositories.
Also, the Arduino supplied gcc toolset is out of date with the latest version of the semi-official Atmel supported "WinAVR" version of gcc, which is also behind the official version of gcc.
For non windows machines, the avr-gcc tools are either built from source or come from a repository and many of the avr-gcc packages in repositories out there are often out of date and lack patch updates.
So in the big picture it is the gcc compiler that would be of most concern to me as it is what controls the actual generated code.
If I were the one maintaining tools and code for a real product, this is the one that would make me sweat, because
depending on which OS and where and when you get your avr-gcc toolset, you will end up with different versions of the compiler, some of which won't generate working code (i.e. the avr-gcc package on pe 9.04 ubuntu) or generate buggy code in certain situations, which is even worse than non working code.
--- bill
From the very low traffic on the developers list I wouldn't expect a 1.0 version this year.
The curent development target is 0019, but (almost) no code has been submitted to the svn yet.
Eberhard
Thanks for all the input. My desire to use a 1.0 version is simply to appeal to perception. I have no concerns about the stability of the compiled code. I have an STK500/stk600 and an MKii with Studio 4. If I don't use the bootloader in the final product, I don't have to explain it. At any rate its not important whether 1.0 is released soon. It just effects how I go about releasing this thing.
There is a beta version 0019 on the Google Code repositories so I expect that to be released before a 1.0
Also, if you read the Arduino Blog they say this...
"....Mega support and a standalone SPI library are coming in Arduino 0019, which should be out later this week...."
So expect 0019 soon. Don't expect 1.0 just yet. I am guessing 2011 at the earliest personally.
If that is the case, you should not be relying on an opensource platform to be developing your project.
Oh, the is nothing wrong with developing a product on open source platforms, plenty are and work just fine. The problem here is that technically arduino is still in alpha (as it says on the about screen).
Ok so 0019 has been out for a few days, I don't see many changes, what about you?
The arduino developers must be very very busy...