Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
In the last weeks it could seems there have been too few movement in the project due to several reasons: NodeOS core is stabilized after the RC1, and both me and other members of the project we have been busy with work and classes (I hope to read my thesis in May! :-D ). At the end, we are working on NodeOS on our spare time and we have some real-life responsabilities...
One recurrent issue people is having is that
But to be honest, upcoming npm 3 support what not the main reason to move cross-toolchain as an independent module, but NodeOS prebuild images. NodeOS build process has got to be so much complex and heavy weight that the CI server was getting random errors constantly (and in fact I'm thinking to move to another one due to this, but I've not found any other free one as fast... maybe is it time to give another opportunity to TravisCI?), so the only possible solution was to split the build process in several independent fragments and test them separately, tha obvious first one was the cross-toolchain since it only would need changes when a new version of GCC or Linux kernel arises. So after adding the dependencies and tuning-up the build scripts and fix some bugs on the publish-release module... finally we have prebuild NodeOS images again after 4 months of silence, just ready so people can test the upcoming 1.0 version :-D
Last but not least, another tiny bit that has been floating around since some time ago was the possibility to add an administrator mode that would allow to admin some system global configs like to allow to
So as you can see, steady NodeOS is moving towards it's 1.0 version! :-D Let's hope the issues that have appear on its dependencies modules can be fixed soon and we can release something we can be proud of :-)