Prepare the engine for release 1.0

[LaszloLango]

This issue is created to collect all the tasks we need to do before the first release of the engine.

Documentation

• GitHub wiki
• gh-pages (http://samsung.github.io/jerryscript)
• In source documentation
  • Comments in public headers files
  • Markdown files under docs folder (internals doc. and API examples&references)
  • Target porting how-to. See: Add documentation to port API #1313

Jerry API

• Finalize Jerry API. See: Jerry API v1.0 #1148

Jerry Port API

• Finalize Jerry Port API. See: Re-thinking the Jerry Port API (proposal) #964

Refactor the build system

• Create new build system. See: Re-thinking the build system (proposal) #998, Re-thinking the build system to bring it more into line with the conv… #1192
• Provide instructions or automate build for the NuttX/RIOT configuration on the STM32F4 board

Release criteria

• Regression tests pass on x86-32 Linux
• Regression tests pass on x86-64 Linux
• Regression tests pass on ARMv7 Linux
• SunSpider benchmark produces correct results running on top of NuttX on the STM32F4 board
• RIOT port passes smoke test (running a hello world script)

Community feedback

• mbed OS 3.0 has been tested and works (running a blinking LED test)
• Various versions of Zephyr have been tested and work (see comments below)

Needs testing support/feedback from the community

• ESP8266, see [esp8266] build failure #1264

[LaszloLango]

I tried to summarize the TODOs for the planned release. Anyone who has write access feel free to edit the description of the issue. Every comment and suggestion is welcome.

[seanshpark]

👍

[seanshpark]

Not sure how to explain but how about usage examples something like target porting how-to, small toy project examples, video clips links... ?

[tilmannOSG]

I've update the issue to reflect the current status :)

[polaroi8d]

Im tested the mbed OS with FRDM-K64F board and the simple blinky example. Its works right ✅

[tilmannOSG]

@polaroi8d Thanks, that's great to hear! Can you please also mention the git hash of the version that you tested?

[polaroi8d]

@tilmannOSG Im tested the 'JerryScript v1.0 Release Candidate 2' source code from github.com/Samsung/jerryscript/releases site, but there is a hash too: 1e82ae1

[tilmannOSG]

@polaroi8d I see, we actually merged the Curie support recently (to make sure that it will be part of the 1.0 release), those changes were not part of the RC2 tarball on Friday. Can you please do another test run with the jerryscript-release-1.0.0 branch?
Thanks in advance!

[polaroi8d]

@tilmannOSG with 7f69111 hash its the same result with the same blinky example. Works fine!

[tilmannOSG]

@polaroi8d Looks like the hash you mentioned is from trunk, please test with https://github.com/Samsung/jerryscript/tree/jerryscript-release-1.0.0 :)
The current HEAD in jerryscript-release-1.0.0 is 04e597a
Can you please give it another try? :)

[bzsolt]

I've checked the x86-32 Linux, x86-64 Linux and ARMv7 Linux targets with the precommit script (tools/run-tests.py --precommit) and everything works fine.
The tested hash is 04e597a