#developers tools

11/05/17Download source

This hotfix is larger than some of the previous fixes, including a fix for the TravisCI build errors.

A single hotfix has been released on Sunday (11/05/17). This hotfix was released to reolve an issue when the Travis CI system ran any homebrew operation, which was fixed simply by updating homebrew on maxOS builds.

8/30/17Download source

So we had another minor build error with the Travis CI service.

A single hotfix has been released on Wednesday (8/30/17). This hotfix was released to reolve an issue when the Travis CI system ran the apt-get operation, which it does not appear we have much control over at this time. The exact error reads: The command "sudo -E apt-get -yq --no-install-suggests --no-install-recommends --force-yes install clang-5.0" failed and exited with 100 during .

6/5/17Download source

So we had some minor build errors with the Travis CI service we use for continuous integration (CI) and cloud testing. Continuous integration and cloud testing is incredibly important in current software development, so fixing these build issues are vital to us at OpenRPG. What cloud testing with Travis CI allows us to do is test OpenRPG in enviroments we normally wouldn't have the opprotunity to test on.

Two hotfixes have been released since Wednesday (5/31/17). The first hotfix was released the same day, and I even snuck in a link change in the Alpha v0.4.0-dev release post, found here. The second hotfix was released this passed Friday (6/2/17) and fixed a very specific build issue with GCC compilation on Linux. Below you can find the change notes for each hotfix that was released for Alpha v0.4.0-dev

5/31/17 Download source

Woah! It’s that time again. There is a lot coming with this update. We are still in alpha, so many of them are very technical, but consider this post the release notes!

For those who do not understand development life cycles (from Wikipedia):

The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white-box techniques. Additional validation is then performed using black-box or gray-box techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.[1]

Alpha software can be unstable and could cause crashes or data loss. Alpha software may not contain all of the features that are planned for the final version.[2] In general, external availability of alpha software is uncommon in proprietary software, while open source software often has publicly available alpha versions. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete.

Why CodePen is best tool for frontend developers?

There are different tools for front-end development. But all developers choose the perfect one that enables better development with security. CodePen is known as the best tool for frontend developers. Whatever design you are thinking about a site you can easily develop it through different types of tools of CodePen. It is a social tool for front end developer and designers. Here you can:

Build a…