even this is not Edison, but it may be the same:
Here are the release notes for the Intel Galileo Board Image:
- Updates to Yocto 1.7.2
- Wyliodrin replaces Wyliodrin Node.js server
- iotkit-comm added
- Updated Node.js to 0.10.38
- Updated to MRAA 0.7.2 & UPM 0.3.1
- iotkit-agent update to 1.7.0
I don't know the answer, but I'm interested as well. I didn't realize there was another release.
I flashed the same image a couple of days ago and would also like to know the answer to your question. According to the format for release ID 25.5-15 was the 25th week of 2015; the previous one I found was 18.5-5. But hat doesn't help much. When I query the version, here's the response:
root@Eddie_1:~# configure_edison --version
I have no clue regarding the relation of '159' to the image release 25.5-15 but would love to have that information.
Another piece of information gathered in examining the flashed image for release 25.5-15. Here are the first few lines of the boot:
PSH KERNEL VERSION: b0182b2b
SCU IPC: 0x800000d0 0xfffce92c
PSH miaHOB version: TNG .B0 .VVBD .0000000c
microkernel built 11:24:08 Feb 5 2015
thanks to for all the answers, it seems to be a maintenance release.
In our case we have 159 as version number, we can call it Release 2.2?
Hi, is there a reason the node that comes installed with the latest image is still 10.38? 12.7 is out, seems very backwards unless there's a specific reason
Thanks for answering, so there isn't a reason for not including the latest node in the latest Release(2.1) ?
An issue i have is jsupm seems incompatible with node >=12.x is that true?
I have tested an example in Node v.0.10.38 and v0.12.4. In version 12 I had some issues but with version 10 it worked fine. Is there a specific reason you want to use node 12? If there isn't a specific reason I suggest you to go back to version 10.
Specific reason- I'm trying to run something that requires node >=12. Also i keep getting undefined errors on node 10 that have been said to be fixed in later updates, but i can't use them because jsupm is broken in node 12 =(
NodeJS 0.12.XX has not been validated with Intel Edison. Updating the current version of NodeJS (0.10.38) could cause compatibility issues. An updated version of NodeJS could be included in a future software release.